Re: linux-x86-tip: pilot error?

[Ingo Molnar <mingo@elte.hu>]

* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> > That would be expected behavior, yes. You can try a "test-pull" into 
> > core/rcu:
> > 
> >   git-checkout -b test-rcu tip/core/rcu
> >   git-merge paulmck-rcu-2008-06-23   # replace with git-pull and an URI
> > 
> > ... and then look at how "git-log test-rcu..linus/master" looks like. It 
> > should show all the changes of the RCU topic, your two new commits 
> > included.
> 
> The git-merge seemed to run normally, but the git-log command showed
> no output.  Hmmm...

sorry, i accidentally reversed the arguments, that should have been:

  git-shortlog linus/master..test-rcu
  git-log linus/master..test-rcu

the way such things can be noticed is to replace git-log with git-diff:

   git-diff test-rcu..linus/master

and if that does not come empty (and it didnt), it's an ordering 
problem.

> >  $ git-describe 481c5346d0981940ee63037eb53e4e37b0735c10
> >  v2.6.26-rc7-25-g481c534
> 
> So this shows the last linus/master commit -not- containing the patch, 
> correct?  Ah, the most recent -tag-.  So I have to be a bit careful 
> about creating tags if I want this to work for me.  Fair enough!

you most definitely need to be careful about creating tags. Tags have 
extra security value (Linus signs them, etc.) and Git will not override 
an existing tag by default in any case. So you definitely dont want to 
create a tag that collides with any expected future upstream tag. (such 
as "v2.6.26" or "2.6.26-rc8")

tags are mostly meant for release management - our use of tags to save 
the "merge base" of topic branches in -tip can be considered mild abuse. 

( But we did not want to pullute the already crowded branch space with 
  extra technical branches. -tip has 127 branches at this moment, 89 of 
  which are topic branches - creating a base branch for each topic would 
  add another 89 branches and bring it all up to 216 branches. )

	Ingo