From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Define upmconfig() for 834x systems
Date: Mon, 11 Sep 2006 12:53:15 -0500 [thread overview]
Message-ID: <4505A28B.9010909@freescale.com> (raw)
In-Reply-To: <1157996270.5069.26.camel@saruman.qstreams.net>
Ben Warren wrote:
> I understand your reluctance to accept code that's not used by any of
> the eval boards and SBCs that are part of the distribution. There are
> many reasons for taking this approach.
I'm working on a patch for the ITX that includes this change, as Wolfgang requested, so it's no big deal.
> A crazy idea that I'm sure has been shot down before, but have you ever
> considered making an 'unstable' branch available? It could contain all
> patches that pass the coding standards and perhaps a week of feedback.
> If there was a big flashing sign that says "Use at your own risk", you
> could offload the "RTFM" responses to others on the list, giving
> yourself more time to move patches from unstable to stable.
I think that's just going to make more work for Wolfgang and not solve any real problems. Patches aren't completely independent of each other - sooner or later he's going to get patches that apply to one tree but not the other.
Anyone who's really interested in unapplied patches can scan the mailing list archives.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2006-09-11 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 21:47 [U-Boot-Users] [PATCH] Define upmconfig() for 834x systems timur at freescale.com
2006-09-08 22:32 ` Wolfgang Denk
2006-09-08 22:50 ` Timur Tabi
2006-09-08 23:05 ` Wolfgang Denk
2006-09-11 17:37 ` Ben Warren
2006-09-11 17:53 ` Timur Tabi [this message]
2006-09-11 18:52 ` Wolfgang Denk
2006-09-11 18:52 ` [U-Boot-Users] 86xx patches? (was [PATCH] Define upmconfig() for 834x systems) Jon Loeliger
2006-09-11 18:46 ` [U-Boot-Users] [PATCH] Define upmconfig() for 834x systems Wolfgang Denk
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=4505A28B.9010909@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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