Re: Computing the number of patches in linux-next tree

From: Harvey Harrison <harvey.harrison@gmail.com>
Date: Jul 22, 2008, 18:23 UTC
Message-ID: <1216751008.13328.17.camel@brick>
In-Reply-To: <7vabg9n93f.fsf@gitster.siamese.dyndns.org>

On Tue, 2008-07-22 at 10:04 -0700, 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.

I thought that was what Stephen has the next/stable branch for:

git log --pretty=oneline --no-merges next/stable..next/master | wc -l

At least for each day you can find the number of patches....I don't think he tags the stable points, so historically that may be a problem.

Harvey