From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCHES for next Merge Window
Date: Tue, 20 Nov 2007 14:41:35 +0100 [thread overview]
Message-ID: <20071120134135.0DB9C2479C@gemini.denx.de> (raw)
Hello to everybody...
...who has sumbitted new patches without waiting for the official
opening of the new merge window.
Please note that I will NOT apply any of these patches yet. And I
recommend all custodians to wait, too.
The plan is as follows:
Grant Likely's patches come first, then comes the drivers reorgani-
zation, and I tend to say that's what goes into 1.3.2 - after such a
significant restructuring I'd rather want to have it tested and
cleaned up first before adding more new stuff. Let's do a quick cycle
for 1.3.2 (which would be also good to bring us back in sync with the
Linux cycle).
In any case, after that probably all patches have to be rebased
against the new tree - otherwise we would run into a lot of nasty
merge conflicts.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Sex is like air. It's only a big deal if you can't get any.
next reply other threads:[~2007-11-20 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 13:41 Wolfgang Denk [this message]
2007-11-20 15:19 ` [U-Boot-Users] PATCHES for next Merge Window Kumar Gala
2007-11-20 15:29 ` Grant Likely
2007-11-20 15:24 ` Grant Likely
2007-11-20 14:36 ` Jean-Christophe PLAGNIOL-VILLARD
2007-11-20 22:03 ` Wolfgang Denk
2007-11-20 17:42 ` Jon Loeliger
2007-11-20 18:05 ` Jerry Van Baren
2007-11-20 20:26 ` Wolfgang Denk
2007-11-20 20:49 ` Josh Boyer
2007-11-20 20:59 ` Grant Likely
2007-11-20 21:06 ` Jon Loeliger
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=20071120134135.0DB9C2479C@gemini.denx.de \
--to=wd@denx.de \
--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