Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit:	trunk/buildroot/target/u-boot/2009.01-rc1
Date: Tue, 06 Jan 2009 16:20:37 +0100	[thread overview]
Message-ID: <1231255237.32308.111.camel@elrond.atmel.com> (raw)
In-Reply-To: <87iqosqz0z.fsf@macbook.be.48ers.dk>

tis 2009-01-06 klockan 15:39 +0100 skrev Peter Korsgaard:
> >>>>> "ulf" == ulf  <ulf@uclibc.org> writes:
> 
>  ulf> Author: ulf
>  ulf> Date: 2009-01-03 00:04:55 +0000 (Sat, 03 Jan 2009)
>  ulf> New Revision: 24656
> 
>  ulf> Log:
>  ulf> Provide factory default command to u-boot, using Buildroot variables
> 
>  ulf> Added:
>  ulf>    trunk/buildroot/target/u-boot/2009.01-rc1/u-boot-2009.01-rc1-009-factory.patch
> 
> Do we really need this? What's the upstream status of it?

I find that this patch reduces maintenance A LOT.
If someone calls in with a problem loading linux,
then you tell them to do "factory"  and then 
everything is SO much easier.

Since it depends heavily on buildroot configuration, 
it makes little sense for this to propagate to upstream.

> 
> I would very much like to limit the number of patches to the minimum
> (E.G. bugfixes, needed hardware support), and this doesn't look like
> either to those.
> 

  reply	other threads:[~2009-01-06 15:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03  0:04 [Buildroot] svn commit: trunk/buildroot/target/u-boot/2009.01-rc1 ulf at uclibc.org
2009-01-06 14:39 ` Peter Korsgaard
2009-01-06 15:20   ` Ulf Samuelsson [this message]
2009-01-06 15:28     ` Peter Korsgaard
2009-01-06 16:03       ` Ulf Samuelsson
  -- 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:06 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
2009-01-03  0:05 ulf at uclibc.org
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=1231255237.32308.111.camel@elrond.atmel.com \
    --to=ulf.samuelsson@atmel.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