Computing the number of patches in linux-next tree

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Computing the number of patches in linux-next tree

From: "Tony Luck" <tony.luck@intel.com>
Date: 2016-06-15 22:44:59

I tried to produce a graph of the pending avalanche of patches
sitting in the linux-next tree and came up with this:

git tag | grep next- | sort | while read tag
do
        c=$(git-rev-list --no-merges $tag ^linus | wc -l)

        echo ${tag##next-} $c
done

Where "linus" is a branch that tracks Linus' tree.  But this gets the
wrong count
for old tags because maintainers who use the topic-branch method have
exactly the same commits in linux-next as eventually end up in Linus ... so
once Linus pulls these trees, the historical counts change.

What I really need at this point is the commit from Linus tree that Stephen
uses as the basis for each next-* tag.  I.e. change the loop body to

       base=`git-where-did-this-tag-branch-from-linus $tag`
       c=$(git-rev-list --no-merges $tag ^$base | wc -l)

Is this the right way to do this?
What does the "git-where-did-this-tag-branch-from-linus" command look like?

-Tony

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

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:44:59

Hi,

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.

Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help