From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] x86 Custodianship
Date: Wed, 26 May 2010 22:13:45 +0200 [thread overview]
Message-ID: <20100526201345.E1839EAC238@gemini.denx.de> (raw)
In-Reply-To: <4BF74992.9000806@gmail.com>
Dear Graeme Russ,
In message <4BF74992.9000806@gmail.com> you wrote:
>
> One quick question - Since I am currently the only x86 developer, how do
> you want to handle the SOB + Ack'd for x86 patches? I feel that to date be
> applying my patches you have implied your own Ack'd By. Should I wait for
> you (or somebody else) to Ack them before I apply them to the x86 repo?
Not necessarily. As long as it's clearly architecture specific code
only, just post the patche son the ML and allow for a number of days
(I think 3 working days should be the minimum, 5 is almost always
enough) and then feel free to apply them.
> I am more than happy (and would prefer) my patches to remain out of the x86
> repo until formally Ack'd
You need a number of x86 developers to get useful technical input; I
don't know much about x86 so all I can usually is do is look at
formal things like coding style violations and such :-(
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
Technology is dominated by those who manage what they do not under-
stand.
prev parent reply other threads:[~2010-05-26 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 12:22 [U-Boot] x86 Custodianship Graeme Russ
2010-05-21 15:11 ` Wolfgang Denk
2010-05-22 3:03 ` Graeme Russ
2010-05-24 8:16 ` Andy Pont
2010-05-26 20:13 ` Wolfgang Denk [this message]
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=20100526201345.E1839EAC238@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.