From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: rename patches as per the new standard and update 1.21.0 mdev
Date: Tue, 23 Apr 2013 11:15:06 -0300 [thread overview]
Message-ID: <5176976A.3090001@zacarias.com.ar> (raw)
In-Reply-To: <8761zde433.fsf@dell.be.48ers.dk>
On 04/23/2013 11:04 AM, Peter Korsgaard wrote:
> Sorry, I disagree with this rename. I know this is what we discussed at
> the dev day, but it imho makes more sense to use the upstream naming
> convention for busybox:
>
> http://busybox.net/downloads/fixes-1.21.0/
>
> Could you send a patch that only updates the mdev bugfix instead?
Sure, i just wanted the official "go" or "no go" as discussed with
Arnout so i went with the renaming to get a definitive answer to the
dilemma.
Maybe an update to the docs is in order to reflect this?
For instance "if upstream has versioned patches then it should be
respected" or something like that?
Regards.
next prev parent reply other threads:[~2013-04-23 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 13:21 [Buildroot] [PATCH] busybox: rename patches as per the new standard and update 1.21.0 mdev Gustavo Zacarias
2013-04-23 14:04 ` Peter Korsgaard
2013-04-23 14:15 ` Gustavo Zacarias [this message]
2013-04-23 21:10 ` Arnout Vandecappelle
2013-04-23 21:42 ` Peter Korsgaard
2013-04-24 6:07 ` Gustavo Zacarias
2013-04-24 6:11 ` 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=5176976A.3090001@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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