From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Richard Fontana <fontana2012@gmail.com>
Cc: "Bradley M. Kuhn" <bkuhn@ebb.org>,
linux-kernel@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH 1/4] copyleft-next: remove issue tracker references
Date: Wed, 11 Jul 2012 17:44:46 -0700 [thread overview]
Message-ID: <1342053889-32066-2-git-send-email-mcgrof@do-not-panic.com> (raw)
In-Reply-To: <1342053889-32066-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
next prev parent reply other threads:[~2012-07-12 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 0:44 [PATCH 0/4] copyleft-next: first set of patches Luis R. Rodriguez
2012-07-12 0:44 ` Luis R. Rodriguez [this message]
2012-07-12 0:44 ` [PATCH 2/4] copyleft-next: more project name updates Copyleft.next->copyleft-next Luis R. Rodriguez
2012-07-12 0:44 ` [PATCH 3/4] copyleft-next: rename the file COPYLEFT.next to copyleft-next Luis R. Rodriguez
2012-07-12 0:44 ` [PATCH 4/4] copyleft-next: embrace the Signed-off-by practice Luis R. Rodriguez
2012-07-12 15:27 ` Ted Ts'o
2012-07-12 17:30 ` Luis R. Rodriguez
2012-07-12 17:57 ` Ted Ts'o
2012-07-12 18:16 ` Luis R. Rodriguez
2012-07-12 19:41 ` Richard Fontana
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=1342053889-32066-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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.