* Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx> wrote: > Trying "git-checkout -b tip-core-rcu > tip-core-rcu-2008-06-16_09.23_Mon" acts like it is doing something > useful, but doesn't find the recent updates, which I believe happened > -before- June 16 2008. finding the rcu topic branch in -tip can be done the following way: $ git-branch -a | grep rcu tip/core/rcu and doing a "git-log tip/core/rcu..linus/master" will show you the commits that are in the tip/core/rcu topic branch. if you check out that branch for your own use, you should also do: $ git-merge linus/master To bring it up to latest upstream. That merge, even if tip/core/rcu looks "old" will always be conflict-free, due to scripting we do: tip-core-rcu-2008-06-16_09.23_Mon is not a snapshot of the rcu topic - it is "technical" tag of the upstream Linus -git tree against which the rcu topic is based. We have to track the 'base' of every topic separately because otherwise we'd pollute the topic branches with the frequent merges to Linus's tree. (occasionally we merge to Linus's tree several times a day, that would lead to tons of merge commits that pollute the tree) So instead we do "on-demand virtual merges": we have scripting which do the following: in each iteration step they merge to latest Linus, check whether there's any files touched by the merge that are changed by the topic branch too - if yes then the merge is made permanent and the "this is this topic's latest upstream" tag is updated. If the merge was conflict-free, we roll back the merge. Is there a Git way of finding the common ancestor of a topic branch, when compared to upstream? Ingo -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
