Re: Computing the number of patches in linux-next tree
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jul 22, 2008, 17:24 UTC
- Message-ID
- <alpine.DEB.1.00.0807221816560.8986@racer>
- In-Reply-To
- <7vabg9n93f.fsf@gitster.siamese.dyndns.org>
Hi,
On Tue, 22 Jul 2008, Junio C Hamano wrote:
Show 17 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > > > On Tue, 22 Jul 2008, Tony Luck wrote: > > > >> git tag | grep next- | sort | while read tag > > > > This should not be necessary... AFAICT "git tag" sorts its output already. > > > >> What does the "git-where-did-this-tag-branch-from-linus" command look like? > > > > git merge-base --all <branch1> <branch2> > > > > Be warned: there might be multiple merge bases. > > I do not think that approach applies to linux-next, which is constantly > rewound to the then-tip-of-linus and merge remaining bits. The question > is "where does this branch begin", which does not have an answer in git.
Oh.
Well, there is one thing that _could_ work most of the time, namely looking at the committer info of the first parent.
Dunno, Dscho