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 00:42:45 +0100 [thread overview]
Message-ID: <20080223234246.0BA9424D0B@gemini.denx.de> (raw)
In-Reply-To: Your message of "Sat, 23 Feb 2008 18:19:55 EST." <200802231819.56414.vapier@gentoo.org>
In message <200802231819.56414.vapier@gentoo.org> you wrote:
>
> > Still the patches need to be reviewed first.
>
> fair enough. i'd point out for the cpu unification, the patch is 400k and i'm
> not about to go splitting it up just so the mailing list will accept it. if
> people actually care, they can read the diff in the git tree.
Mike, this is not the way you are supposed to react - not as a norman
developer, and escpecially not as a custodian.
You want the stuff to go in, so please make it easy for us to review
it.
> > In cases like this one, where there is a custodian who caresa about
> > the topic of the patches, I wait for his pull request and then pull
> > from the repo. The posting of the patches is primarily for giving
> > others a chance to review the stuff *before* it goes into mainline.
>
> so for all Blackfin patches, i'll post them and people may review them, but
> you wont merge them until i put them into my tree for you to pull ?
Correct - except that you already have those patches in some git
repository, because otherwise you could not use git-format-patch and
git-send-email to prepare resp. to send the patches.
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
The price of curiosity is a terminal experience.
- Terry Pratchett, _The Dark Side of the Sun_
next prev parent reply other threads:[~2008-02-23 23:42 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
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 [this message]
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=20080223234246.0BA9424D0B@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.