git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Computing the number of patches in linux-next tree

From
Tony Luck <tony.luck@intel.com>
Date
Jul 22, 2008, 16:19 UTC
Message-ID
<12c511ca0807220919q4db6ee1fr33dc70fe35c58efe@mail.gmail.com>

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
Next: Johannes Schindelin
Message 1 of 6 in “Computing the number of patches in linux-next tree”
  1. Tony LuckJul 22, 2008
  2. Johannes SchindelinJul 22, 2008
  3. Junio C HamanoJul 22, 2008
  4. Luck, TonyJul 22, 2008
  5. Johannes SchindelinJul 22, 2008
  6. Harvey HarrisonJul 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.