From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Download patches for Busybox
Date: Wed, 24 Apr 2013 15:54:23 +0200 [thread overview]
Message-ID: <20130424155423.382dc054@skate> (raw)
In-Reply-To: <8738ugcvdw.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Wed, 24 Apr 2013 08:09:31 +0200, Peter Korsgaard wrote:
> Thomas> Hello,
> Thomas> As recently discussed on the list, here are two patches that
> Thomas> let the busybox package download its patches, instead of
> Thomas> storing them in Buildroot's source tree.
>
> Thanks. There's one big problem with busybox though. Denys tends to
> update the patches without renaming them if more problems are found in
> those applets - So we end up with different results depending on when
> you build.
Yerk, this is ugly.
> Perhaps we can convince him to do otherwise, but until then I would
> prefer to keep it like it is.
Indeed, in this case, we don't have much choice.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-24 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 2:22 [Buildroot] [PATCH 0/2] Download patches for Busybox Thomas Petazzoni
2013-04-24 2:22 ` [Buildroot] [PATCH 1/2] package: use only the patch file name when applying patches Thomas Petazzoni
2013-04-24 2:22 ` [Buildroot] [PATCH 2/2] busybox: download patches instead of storing them in the source tree Thomas Petazzoni
2013-04-24 6:09 ` [Buildroot] [PATCH 0/2] Download patches for Busybox Peter Korsgaard
2013-04-24 13:54 ` Thomas Petazzoni [this message]
2013-04-26 5:58 ` Arnout Vandecappelle
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=20130424155423.382dc054@skate \
--to=thomas.petazzoni@free-electrons.com \
--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