From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Pull request u-boot-blackfin.git
Date: Sat, 23 Feb 2008 18:19:55 -0500 [thread overview]
Message-ID: <200802231819.56414.vapier@gentoo.org> (raw)
In-Reply-To: <20080223223002.86E2A243AB@gemini.denx.de>
On Saturday 23 February 2008, Wolfgang Denk wrote:
> In message <200802231529.04407.vapier@gentoo.org> you wrote:
> > > Then that cannot go in now. We would break several rules at once:
> > > patches must be posted to the list first, and new stuff will get
> > > merged only when a merge window is open.
> >
> > since Blackfin literrally has never compiled/linked in the mainline
> > releases, theres no way i could break it even more. delaying these
> > updates to make mainline Blackfin u-boot usable is only that: delay.
>
> 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.
> > as for posting the patches to the list, how do you know whether to merge
> > it directly or pull from a repo ?
>
> 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 ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080223/7896d95e/attachment.pgp
next prev parent reply other threads:[~2008-02-23 23:19 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 [this message]
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=200802231819.56414.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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.