From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Pull request u-boot-blackfin.git
Date: Sun, 24 Feb 2008 02:22:25 +0100 [thread overview]
Message-ID: <20080224012225.D40BC24D0B@gemini.denx.de> (raw)
In-Reply-To: Your message of "Sat, 23 Feb 2008 19:39:51 EST." <200802231939.51739.vapier@gentoo.org>
In message <200802231939.51739.vapier@gentoo.org> you wrote:
>
> of course i have. writing out rules is to codify the spirit of the process so
> that people can jump in and know how things works. however, the point of the
> rules isnt to have a rigid unchanging methodology, but to keep things flowing
> in the spirit: merge windows allow new fun stuff while the non-merge time is
> for bugfixes only. this of course assumes that the tree in question is
> stable/usable in the first place. if it isnt, then there isnt much point to
> locking out changes to move it in that direction.
The tree in general is actually pretty stable/usable as of now; I
know only of a few (minor) problems.
If the BF stuff is in bad shape, then I'm sorry about this, but 1)
you could have posted your stuff in the merge window like everybody
else, or 2) you have to wait until the next merge window like
everybody else. I will not destabilize the whole tree for a single
architecture.
If you have bug fixes, please go on and post these and I will make
sure they go in as fast as possible.
But I will not add major new code now.
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
Q: How do you play religious roulette?
A: You stand around in a circle and blaspheme and see who gets
struck by lightning first.
next prev parent reply other threads:[~2008-02-24 1:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 6:17 [U-Boot-Users] Pull request u-boot-blackfin.git Mike Frysinger
2008-02-23 8:42 ` Wolfgang Denk
2008-02-23 8:59 ` Mike Frysinger
2008-02-23 19:36 ` Wolfgang Denk
2008-02-23 20:29 ` Mike Frysinger
2008-02-23 22:25 ` Haavard Skinnemoen
2008-02-23 23:17 ` Mike Frysinger
2008-02-23 23:50 ` Haavard Skinnemoen
2008-02-24 0:07 ` Mike Frysinger
2008-02-24 0:29 ` Wolfgang Denk
2008-02-24 0:39 ` Mike Frysinger
2008-02-24 1:22 ` Wolfgang Denk [this message]
2008-02-24 1:37 ` Mike Frysinger
2008-02-24 13:44 ` Wolfgang Denk
2008-02-24 0:35 ` Haavard Skinnemoen
2008-02-24 1:15 ` Mike Frysinger
2008-02-24 13:55 ` Jean-Christophe PLAGNIOL-VILLARD
2008-02-24 16:48 ` Mike Frysinger
2008-02-23 22:30 ` Wolfgang Denk
2008-02-23 23:19 ` Mike Frysinger
2008-02-23 23:42 ` Wolfgang Denk
2008-02-24 0:09 ` Mike Frysinger
2008-02-24 0:36 ` Wolfgang Denk
2008-02-24 1:18 ` Mike Frysinger
2008-02-24 1:26 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2008-06-01 2:59 Mike Frysinger
2008-06-01 19:45 ` Wolfgang Denk
2008-06-01 20:54 ` Mike Frysinger
2008-06-01 21:54 ` Wolfgang Denk
2008-06-01 22:02 ` Mike Frysinger
2008-06-01 22:15 ` Wolfgang Denk
2008-06-01 22:47 ` Mike Frysinger
2008-06-02 11:58 ` Wolfgang Denk
2008-03-30 19:54 Mike Frysinger
2008-04-07 22:09 ` Wolfgang Denk
2008-03-16 2:33 Mike Frysinger
2008-03-18 21:17 ` Wolfgang Denk
2008-02-24 1:33 Wolfgang Denk
2008-02-05 0:31 Mike Frysinger
2008-02-14 23:12 ` 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=20080224012225.D40BC24D0B@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 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.