Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] busybox: 1.21.1 fix for move_to_unaligned16()
Date: Wed, 27 Feb 2013 22:19:56 +0100	[thread overview]
Message-ID: <512E787C.9090303@mind.be> (raw)
In-Reply-To: <874ngx5vn5.fsf@dell.be.48ers.dk>

On 27/02/13 21:50, Peter Korsgaard wrote:
>>>>>> >>>>>"Arnout" == Arnout Vandecappelle<arnout@mind.be>  writes:
>   Arnout> On 27/02/13 15:57, Peter Korsgaard wrote:
>   >> commit:http://git.buildroot.net/buildroot/commit/?id=d8024d2d87864eb0ba381291e0e2986f7643c8dc
>   >> branch:http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>   >>
>   >> Signed-off-by: Peter Korsgaard<jacmet@sunsite.dk>
>   >> ---
>   >> .../busybox-1.21.0/busybox-1.21.0-platform.patch   |   11 +++++++++++
>   >> 1 files changed, 11 insertions(+), 0 deletions(-)
>   >>
>   >> diff --git a/package/busybox/busybox-1.21.0/busybox-1.21.0-platform.patch b/package/busybox/busybox-1.21.0/busybox-1.21.0-platform.patch
>   >> new file mode 100644
>   >> index 0000000..2401b86
>   >> --- /dev/null
>   >> +++ b/package/busybox/busybox-1.21.0/busybox-1.21.0-platform.patch
>   >> @@ -0,0 +1,11 @@
>
>   Arnout>  Why do we bother to tell our contributors to add a patch description
>   Arnout> and Signed-off-by if our maintainer doesn't even do it?:-)
>
> Mainly because busybox upstream unfortunately doesn't do it even though
> he has been asked.
>
> But ok, I guess I could dig through busybox git and come up with a
> description

  In that case you could even do a format-patch.


> or atleast link to the upstream location.

  That's what I mean:

  - copy your own commit message text into the patch;

  - mention the upstream URL 
http://busybox.net/downloads/fixes-1.21.0/busybox-1.21.0-platform.patch

  - Add your Sob.


  Actually, I don't even really want to claim that this is the way it 
_should_ be done. Rather, it is what I as a reviewer tell our 
contributors, because that's what I understand our policy is.


> Upstream unfortunately also updates these files without renaming them.

  That is... unfortunate.  Otherwise we could apply them directly with 
BUSYBOX_PATCH (after the patch that allows foreign URLs has been applied).


  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

      reply	other threads:[~2013-02-27 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 14:57 [Buildroot] [git commit] busybox: 1.21.1 fix for move_to_unaligned16() Peter Korsgaard
2013-02-27 19:29 ` Arnout Vandecappelle
2013-02-27 20:50   ` Peter Korsgaard
2013-02-27 21:19     ` Arnout Vandecappelle [this message]

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=512E787C.9090303@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