From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/u-boot/2009.01-rc1
Date: Tue, 06 Jan 2009 19:13:21 +0100 [thread overview]
Message-ID: <87bpuknvzy.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1231262543.32308.189.camel@elrond.atmel.com> (Ulf Samuelsson's message of "Tue\, 06 Jan 2009 18\:22\:23 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Ulf> If you want to avoid cluttering the u-boot directory
Ulf> with patches, then it is of course a possibility
Ulf> to apply all patches and store the tarball on $(ATMEL_MIRROR)
Ulf> That will make the patches harder to maintain and
Ulf> it will take longer to get them into mainline.
Why? Having them in buildroot or not seems pretty unrelated to their
upstream acceptance or not.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-06 18:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 0:06 [Buildroot] svn commit: trunk/buildroot/target/u-boot/2009.01-rc1 ulf at uclibc.org
2009-01-06 14:37 ` Peter Korsgaard
2009-01-06 15:16 ` Ulf Samuelsson
2009-01-06 15:26 ` Peter Korsgaard
2009-01-06 15:56 ` Ulf Samuelsson
2009-01-06 16:18 ` Peter Korsgaard
2009-01-06 17:22 ` Ulf Samuelsson
2009-01-06 18:13 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-06 16:24 ulf at uclibc.org
2009-01-06 16:24 ulf at uclibc.org
2009-01-06 16:33 ` Peter Korsgaard
2009-01-06 16:21 ulf at uclibc.org
2009-01-06 16:17 ulf at uclibc.org
2009-01-06 16:17 ulf at uclibc.org
2009-01-06 16:32 ` Peter Korsgaard
2009-01-06 16:13 ulf at uclibc.org
2009-01-06 16:10 ulf at uclibc.org
2009-01-06 16:09 ulf at uclibc.org
2009-01-03 0:05 ulf at uclibc.org
2009-01-03 0:04 ulf at uclibc.org
2009-01-06 14:39 ` Peter Korsgaard
2009-01-06 15:20 ` Ulf Samuelsson
2009-01-06 15:28 ` Peter Korsgaard
2009-01-06 16:03 ` Ulf Samuelsson
2009-01-03 0:04 ulf at uclibc.org
2009-01-03 0:03 ulf at uclibc.org
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=87bpuknvzy.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.