Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] docs/website: contribute.txt update with useful tips on patch versioning and patch submission
Date: Tue, 8 Sep 2015 17:03:33 +0200	[thread overview]
Message-ID: <55EEF8C5.3000109@mind.be> (raw)
In-Reply-To: <1619019.BvyX3KbBJD@deathstar>



On 08-09-15 16:57, Francesco Nwokeka wrote:
> On Tuesday 08 September 2015 15:46:36 Arnout Vandecappelle wrote:
>> On 08-09-15 15:22, Francesco Nwokeka wrote:
>>> Added an alternative on patch versioning (the -v option) and added a tip on how to automatically mark a previous commit as superseded
>>>
>>> Signed-off-by: Francesco Nwokeka <francesco.nwokeka@gmail.com>
>>> ---
>>>  docs/manual/contribute.txt | 9 +++++++++
>>>  1 file changed, 9 insertions(+)
>>>
>>> diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
>>> index 40579f9..1ab8ef8 100644
>>> --- a/docs/manual/contribute.txt
>>> +++ b/docs/manual/contribute.txt
>>> @@ -298,6 +298,12 @@ $ git format-patch --subject-prefix "PATCH v4" \
>>>      -M -s -o outgoing origin/master
>>>  ---------------------
>>>  
>>> +or the +-v <n>+ flag (where <n> is the version number):
>>> +
>>> +---------------------
>>> +$ git format-patch -v4 -M -s -o outgoing origin/master
>>> +---------------------
>>> +
>>
>> This option exists since git v1.8.1
> 
> Am I to specify the git version on the documentation or was it just a "fyi" statement?

 Yes, it should be mentioned in the documentation, otherwise people will try the
-v option and wonder why it doesn't work.

 Regards,
 Arnout


[snip]
-- 
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-09-08 15:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 13:22 [Buildroot] [PATCH 1/1] docs/website: contribute.txt update with useful tips on patch versioning and patch submission Francesco Nwokeka
2015-09-08 13:46 ` Arnout Vandecappelle
2015-09-08 14:57   ` Francesco Nwokeka
2015-09-08 15:03     ` Arnout Vandecappelle [this message]
2015-09-08 15:28 ` [Buildroot] [PATCH v2 " Francesco Nwokeka
2015-09-08 15:32   ` Arnout Vandecappelle
2015-09-08 15:47   ` [Buildroot] [PATCH v3 " Francesco Nwokeka
2015-09-15 14:03     ` Fabio Porcedda
2015-09-15 20:35       ` Arnout Vandecappelle
2015-09-19 13:57     ` Thomas Petazzoni

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=55EEF8C5.3000109@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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