From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] packages/Config.in: Fix case on entries titles
Date: Fri, 25 Oct 2013 10:06:17 +0200 [thread overview]
Message-ID: <526A2679.1010606@mind.be> (raw)
In-Reply-To: <CAAXf6LXQn-Ssw13BC3VxCqQLP-c0--5RD-ZduBhZ_64LWiodgQ@mail.gmail.com>
On 25/10/13 08:27, Thomas De Schampheleire wrote:
> Hi Maxime,
>
> On Thu, Oct 24, 2013 at 5:35 PM, Maxime Hadjinlian
> <maxime.hadjinlian@gmail.com> wrote:
>> ---
>> package/Config.in | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/package/Config.in b/package/Config.in
>> index ebbdeb5..8519f45 100644
>> --- a/package/Config.in
>> +++ b/package/Config.in
>> @@ -169,7 +169,7 @@ source "package/gnuplot/Config.in"
>> source "package/jhead/Config.in"
>> source "package/rrdtool/Config.in"
>>
>> -comment "graphic libraries"
>> +comment "Graphic libraries"
>> source "package/cegui06/Config.in"
>> source "package/directfb/Config.in"
>> source "package/directfb-examples/Config.in"
>> @@ -196,7 +196,7 @@ source "package/sdl_net/Config.in"
>> source "package/sdl_sound/Config.in"
>> source "package/sdl_ttf/Config.in"
>>
>> -comment "other GUIs"
>> +comment "Other GUIs"
>> source "package/efl/Config.in"
>> source "package/qt/Config.in"
>>
>> @@ -241,7 +241,7 @@ source "package/liberation/Config.in"
>> source "package/libsexy/Config.in"
>> source "package/x11r7/xkeyboard-config/Config.in"
>>
>> -comment "X Window managers"
>> +comment "X window managers"
>> source "package/blackbox/Config.in"
>> source "package/enlightenment/Config.in"
>> source "package/fluxbox/Config.in"
>
> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
>
> Maxime, when you send multiple versions of a patch, could you use v2,
> v3, ... in the subject line (PATCH v2) to make it easier for reviewers
Note that you can do this with git-send-email (or format-patch):
git send-email -v2 # Send out PATCH v2, requires git >= 1.8.something
git send-email --subject-prefix 'PATCH v2'
Regards,
Arnout
> to distinghuish the different versions? Also below the changelog you
> should put a description of the changes compared to the previous
> version.
> See http://buildroot.uclibc.org/downloads/manual/manual.html#_patch_revision_changelog
>
> Also, I believe it is customary to resend the entire series when there
> is a revision of one of its patches.
>
> Thanks,
> Thomas
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind 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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-10-25 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 15:35 [Buildroot] [PATCH] packages/Config.in: Fix case on entries titles Maxime Hadjinlian
2013-10-25 6:27 ` Thomas De Schampheleire
2013-10-25 8:06 ` Arnout Vandecappelle [this message]
2013-10-25 8:28 ` Maxime Hadjinlian
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=526A2679.1010606@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