Re: git-pull-request for omap2-upstream branch for next merge window (Was: [PATCH 00/16] Omap2 patches for post 2.6.26)

[Tony Lindgren <tony@atomide.com>]

* Russell King - ARM Linux <linux@arm.linux.org.uk> [080826 11:50]:
> On Tue, Aug 26, 2008 at 02:28:14PM -0400, Nicolas Pitre wrote:
> > On Tue, 26 Aug 2008, Nicolas Pitre wrote:
> > 
> > > That's not all black or white.  Many people have branches which are 
> > > rebased all the time, especially when those branches are made up of 
> > > other evolving branches.  I Think this is the case of your devel branch 
> > > which sounds pretty fine to me.  As long as the volatile nature of such 
> > > branch is clearly advertised and people are told not to base their own 
> > > work on of course, and I think you did so many times now.
> > 
> > And I've just seen the commit message of the top commit in the devel 
> > branch.  :-)  If that is not effective then I don't know what might be.
> 
> Well, the theory is that it'll appear in any pull requests generated
> by git-request-pull, and of course everyone reads the output of that
> command before they mail it, don't they?  ;)

Heh, I'll rebase on top of the earlier pull.

Tony