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>,
	linux-kernel@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH 4/4] copyleft-next: embrace the Signed-off-by practice
Date: Wed, 11 Jul 2012 17:44:49 -0700	[thread overview]
Message-ID: <1342053889-32066-5-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>

The idea is taken from Linus Torvald's subsurface
project [0] README file. The Signed-off-by is widely
used in public projects and we stand to gain to make
its usage more prevalent. The meaning of the
Signed-off-by is borrowed from the Linux kernel's.

[0] git://github.com/torvalds/subsurface.git

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
 CONTRIBUTING |   30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 8f214b1..966366c 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -5,6 +5,36 @@ All original contributions to copyleft-next are dedicated to the
 public domain to the maximum extent permitted by applicable law,
 pursuant to CC0. See CC0 for further details.
 
+Please either send me signed-off patches or a pull request with
+signed-off commits.  If you don't sign off on them, I will not accept
+them. This means adding a line that says "Signed-off-by: Name <email>"
+at the end of each commit, indicating that you wrote the code and have
+the right to pass it on as an open source patch.
+
+See: http://gerrit.googlecode.com/svn/documentation/2.0/user-signedoffby.html
+
+Also, please write good git commit messages.  A good commit message
+looks like this:
+
+	Header line: explaining the commit in one line
+
+	Body of commit message is a few lines of text, explaining things
+	in more detail, possibly giving some background about the issue
+	being fixed, etc etc.
+
+	The body of the commit message can be several paragraphs, and
+	please do proper word-wrap and keep columns shorter than about
+	74 characters or so. That way "git log" will show things
+	nicely even when it's indented.
+
+	Reported-by: whoever-reported-it
+	Signed-off-by: Your Name <youremail@yourhost.com>
+
+where that header line really should be meaningful, and really should be
+just one line.  That header line is what is shown by tools like gitk and
+shortlog, and should summarize the change in one readable line of text,
+independently of the longer explanation.
+
 Contributions from individual free/libre/open source software project
 participants, regardless of their views on copyleft, and regardless of
 their opinions on existing licenses such as the GNU GPLv2 and its
-- 
1.7.10.rc1.22.gf5241


  parent reply	other threads:[~2012-07-12  0:46 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 ` [PATCH 1/4] copyleft-next: remove issue tracker references Luis R. Rodriguez
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 ` Luis R. Rodriguez [this message]
2012-07-12 15:27   ` [PATCH 4/4] copyleft-next: embrace the Signed-off-by practice 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-5-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome