Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] docs/manual/contribute.txt: add formatting patches section
Date: Mon, 8 Feb 2016 15:33:28 +0100	[thread overview]
Message-ID: <56B8A738.6010602@mind.be> (raw)
In-Reply-To: <CAGm1_kv+suYiJPKwhwQ4jYPq8KuGMBQRhWH5uGfh53KXzAbQSg@mail.gmail.com>



On 08-02-16 11:48, Yegor Yefremov wrote:
> On Mon, Feb 1, 2016 at 6:45 PM, Arnout Vandecappelle (Essensium/Mind)
> <arnout@mind.be> wrote:

[snip]
>> +The summary line should be something like +<packagename>: bump to version <new
>> +  version>+.
> 
> For now bump message looks so:
> 
> packagename: bump to <new version>
> 
> should we keep it this way, i.e. without the word "version"?

 Since 2015.02, we have:

 89 times '<pkg>: bump version'
382 times '<pkg>: bump version to ...'
816 times '<pkg>: bump to version ...'


 Regards,
 Arnout

> 
>> +If the new version only contains security updates compared to the existing one,
>> +  the summary should be +<packagename>: security bump to version <new version>+
> 
> same here
> 
>> +  and the commit message body should show the CVE numbers that are fixed.
>> +If some package patches can be removed in the new version, it should be
>> +  explained explicitly why they can be removed, preferably with the upstream
>> +  commit ID.
>> +Also any other required changes should be explained explicitly, like configure
>> +  options that no longer exist or are no longer needed.
>> +
>> +
>>  ==== Preparing a patch series
>>
>>  Starting from the changes committed in your local git view, _rebase_ your
>> --
>> 2.7.0
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
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:[~2016-02-08 14:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 17:45 [Buildroot] [PATCH 0/4] docs: improve submitting patches Arnout Vandecappelle
2016-02-01 17:45 ` [Buildroot] [PATCH 1/4] README: add reference to submitting-patches Arnout Vandecappelle
2016-02-01 18:20   ` Thomas Petazzoni
2016-02-01 17:45 ` [Buildroot] [PATCH 2/4] website: add reference to submitting-patches to Contribute tab Arnout Vandecappelle
2016-02-01 18:20   ` Thomas Petazzoni
2016-02-01 17:45 ` [Buildroot] [PATCH 3/4] docs/manual/contribute.txt: add section for preparing patch series Arnout Vandecappelle
2016-02-22 14:23   ` Yegor Yefremov
2016-02-23 23:07   ` Thomas Petazzoni
2016-02-01 17:45 ` [Buildroot] [PATCH 4/4] docs/manual/contribute.txt: add formatting patches section Arnout Vandecappelle
2016-02-08 10:48   ` Yegor Yefremov
2016-02-08 14:33     ` Arnout Vandecappelle [this message]
2016-02-22 14:24       ` Yegor Yefremov
2016-02-23 23:08   ` 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=56B8A738.6010602@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