From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips
Date: Sat, 25 Apr 2009 00:18:44 -0700 [thread overview]
Message-ID: <49F2B954.5040408@gmail.com> (raw)
In-Reply-To: <200904250003.51845.david-b@pacbell.net>
Hi David,
David Brownell wrote:
> On Friday 24 April 2009, Ben Warren wrote:
>
>> My approach is that once the merge window closes, new patches that are not
>> bug fixes go into 'next', which is for the release after the current one (in
>> this case 07).
>>
>
> Then I'm curious how that dm9000 EEPROM reading bugfix
> landed in net/next ... or is the point that the merge
> window for 2009.05 is still open, since RC1 hasn't yet
> been tagged?
>
>
In this case a pretty good argument could be made that it's a bug fix
and not a feature, so can go in 2009.05. Obviously bugs that break
builds get more attention than ones that have been in code for a while
and nobody noticed. I'll ask Wolfgang to pick it up directly. As
you're noticing, how and when patches are picked up is open to many
interpretations.
regards,
Ben
next prev parent reply other threads:[~2009-04-25 7:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 22:44 [U-Boot] [PATCH u-boot git] there are non-DM6446 DaVinci chips David Brownell
2009-04-17 5:44 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-17 6:31 ` David Brownell
2009-04-17 7:28 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-18 21:00 ` David Brownell
2009-04-24 16:24 ` Hugo Villeneuve
2009-04-24 19:33 ` David Brownell
2009-04-24 21:45 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-24 22:40 ` David Brownell
2009-04-25 5:17 ` [U-Boot] U-Boot ARM merge strategy, was: " Dirk Behme
2009-04-25 6:27 ` Ben Warren
2009-04-25 7:03 ` David Brownell
2009-04-25 7:18 ` Ben Warren [this message]
2009-04-25 8:05 ` David Brownell
2009-04-25 10:48 ` Wolfgang Denk
2009-04-25 11:40 ` Dirk Behme
2009-04-25 12:55 ` [U-Boot] U-Boot ARM merge strategy David Brownell
2009-04-25 13:53 ` Wolfgang Denk
2009-04-25 18:53 ` David Brownell
2009-04-26 21:38 ` Wolfgang Denk
2009-04-27 13:44 ` [U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips Jerry Van Baren
2009-04-27 14:00 ` Wolfgang Denk
2009-04-25 10:30 ` Wolfgang Denk
2009-04-25 7:07 ` [U-Boot] U-Boot ARM merge strategy Dirk Behme
2009-04-25 7:42 ` Ben Warren
2009-04-25 10:46 ` Wolfgang Denk
2009-04-25 11:35 ` Dirk Behme
2009-04-25 13:44 ` Wolfgang Denk
2009-04-27 15:47 ` Detlev Zundel
2009-04-27 19:42 ` Wolfgang Denk
2009-04-28 8:32 ` Detlev Zundel
2009-04-28 9:07 ` Wolfgang Denk
2009-04-25 16:13 ` Ben Warren
2009-04-26 5:15 ` Dirk Behme
2009-04-25 10:41 ` Wolfgang Denk
2009-04-25 17:08 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-25 17:30 ` Wolfgang Denk
2009-04-25 18:02 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-25 18:55 ` David Brownell
2009-04-25 6:57 ` [U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips David Brownell
2009-04-25 7:11 ` Dirk Behme
2009-04-24 23:46 ` [U-Boot] [PATCH u-boot git] " Ben Warren
2009-04-25 0:36 ` David Brownell
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=49F2B954.5040408@gmail.com \
--to=biggerbadderben@gmail.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