From: Michael Hope <michael.hope@linaro.org>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: [PATCH] Documented how to format description lines for packages patches
Date: Thu, 29 Sep 2011 02:18:00 -0000 [thread overview]
Message-ID: <fa983e475cfb603465dc.1317262689@crucis> (raw)
# HG changeset patch
# User Michael Hope <michael.hope@linaro.org>
# Date 1317262608 -46800
# Node ID fa983e475cfb603465dcae5cdcd2de67a608ae59
# Parent 69e6e581338dc4558d87fdcde9d9cbf8466893c9
Documented how to format description lines for packages patches.
Added a note on enforcing Signed-off-by lines.
Signed-off-by: Michael Hope <michael.hope@linaro.org>
diff -r 69e6e581338d -r fa983e475cfb docs/7 - Contributing to crosstool-NG.txt
--- a/docs/7 - Contributing to crosstool-NG.txt Thu Sep 29 12:40:42 2011 +1300
+++ b/docs/7 - Contributing to crosstool-NG.txt Thu Sep 29 15:16:48 2011 +1300
@@ -21,6 +21,13 @@
If you want to enhance crosstool-NG, there's a to-do list in the TODO file.
+When updating a package, please include the category and package in the
+start of the description. For example:
+ binutils/binutils: add the 2.22 release
+
+or:
+ cc/gcc: update to the Linaro 2011.09 release
+
Patches should come with the appropriate SoB line. A SoB line is typically
something like:
Signed-off-by: John DOE <john.doe@somewhere.net>
@@ -28,6 +35,11 @@
The SoB line is clearly described in Documentation/SubmittingPatches , section
12, of your favourite Linux kernel source tree.
+Add the following to your ~/.hgrc to make Mercurial check for the SoB
+line when committing:
+ [hooks]
+ pretxncommit.signoff = hg log --template '{desc}\n' -r $HG_NODE \
+ | grep -qi '^signed-off-by:'
For larger or more frequent contributions, mercurial should be used.
There is a nice, complete and step-by-step tutorial in section 'C'.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2011-09-29 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 2:18 Michael Hope [this message]
2011-10-08 20:03 ` Yann E. MORIN
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=fa983e475cfb603465dc.1317262689@crucis \
--to=michael.hope@linaro.org \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).