From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] busybox: move patches to new model
Date: Mon, 22 Apr 2013 23:19:22 +0200 [thread overview]
Message-ID: <5175A95A.90006@mind.be> (raw)
In-Reply-To: <51758AD3.9040207@zacarias.com.ar>
On 22/04/13 21:09, Gustavo Zacarias wrote:
> On 04/22/2013 03:18 PM, Arnout Vandecappelle wrote:
>> I believe the idea was to have plain NNNN-xxxx.patch files (without
>> package or version number) in the patch directories - like is the case
>> already for gcc and gdb. But check the developer day report to be sure.
>>
>> And while you're at it, numbering the patches would be nice.
>
> Historically the busybox patches were left untouched (simple wget, no
> SoB and such).
> If Peter is OK with following the standard i couldn't agree more and
> send a V2 :)
I'm just talking about the filename, not the contents of the patches.
Regards,
Arnout
--
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-04-22 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 14:47 [Buildroot] [PATCH 1/2] busybox: move patches to new model Gustavo Zacarias
2013-04-22 14:47 ` [Buildroot] [PATCH 2/2] binutils: " Gustavo Zacarias
2013-04-22 18:18 ` [Buildroot] [PATCH 1/2] busybox: " Arnout Vandecappelle
2013-04-22 19:09 ` Gustavo Zacarias
2013-04-22 21:19 ` Arnout Vandecappelle [this message]
2013-04-23 7:05 ` Peter Korsgaard
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=5175A95A.90006@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