mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Richard Fontana <fontana2012@gmail.com>
Cc: "Bradley M. Kuhn" <bkuhn@ebb.org>,
	tytso@mit.edu, linux-kernel@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH v2 1/6] copyleft-next: remove issue tracker references
Date: Thu, 12 Jul 2012 10:48:40 -0700	[thread overview]
Message-ID: <1342115325-9443-2-git-send-email-mcgrof@do-not-panic.com> (raw)
In-Reply-To: <1342115325-9443-1-git-send-email-mcgrof@do-not-panic.com>

From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>

This uses github, lets not confuse the focus for
development for now.
---
 CONTRIBUTING |   13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 1db3cd2..d06f5da 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -47,15 +47,4 @@ Public Source Locations
 =======================
 
 Gitorious (https://gitorious.org/copyleft-next) is now the centralized
-location of source for this project. It will be mirrored at a GitHub
-repo (currently https://github.com/richardfontana/Copyleft.next) for
-the time being, and perhaps indefinitely.
-
-
-Issue Tracking
-==============
-
-The issue tracker associated with
-https://github.com/richardfontana/Copyleft.next shall be kept open for the
-time being, but at some point it is likely to be disabled.
-
+location of source for this project.
-- 
1.7.10.rc1.22.gf5241


  reply	other threads:[~2012-07-12 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 17:48 [PATCH v2 0/6] copyleft-next: project name / remove anti-tivoization clause Luis R. Rodriguez
2012-07-12 17:48 ` Luis R. Rodriguez [this message]
2012-07-12 17:48 ` [PATCH v2 2/6] copyleft-next: more project name updates Copyleft.next->copyleft-next Luis R. Rodriguez
2012-07-12 17:48 ` [PATCH v2 3/6] copyleft-next: rename the file COPYLEFT.next to copyleft-next Luis R. Rodriguez
2012-07-12 17:48 ` [PATCH v2 4/6] copyleft-next: embrace the Signed-off-by practice Luis R. Rodriguez
2012-07-12 17:48 ` [PATCH v2 5/6] copyleft-next: remove section 7 - anti-tivoization Luis R. Rodriguez
2012-07-12 18:19   ` Alan Cox
2012-07-12 17:48 ` [PATCH v2 6/6] copyleft-next: re-enumerate sections Luis R. Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1342115325-9443-2-git-send-email-mcgrof@do-not-panic.com \
    --to=mcgrof@do-not-panic.com \
    --cc=bkuhn@ebb.org \
    --cc=fontana2012@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome