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

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

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 22, 2008, 16:28 UTC
Message-ID
<alpine.DEB.1.00.0807221727210.8986@racer>
In-Reply-To
<12c511ca0807220919q4db6ee1fr33dc70fe35c58efe@mail.gmail.com>
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

Previous: Tony LuckNext: Junio C Hamano
Message 2 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.