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

Re: git tag --no-merged?

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 4, 2015, 21:27 UTC
Message-ID
<xmqq1tm5nz9l.fsf@gitster.dls.corp.google.com>
In-Reply-To
<54D26B7C.7020300@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
Show 6 quoted lines
> Am 04.02.2015 um 16:19 schrieb Peter Krefting:
>> Using "git branch --no-merged" I can get a list of branches that I have
>> that I haven't merged into my current branch.
>
> Assuming v2.0.0 is a tag, using "git branch --no-merged v2.0.0" you can
> see which branches haven't been merged into v2.0.0.

I think the request is a bit more involved than "Which one is not yet in v2.0.0?"

The question, as I now understand it after reading it again, 
    I want to merge the changes from the maintenance branches to
    master (and possibly to other maintenance branches if there are
    changes relevant to other products), but I only want to do this for
    our tagged released.

is "which branches, whose tips are already tagged, are not yet in 'master'?"

The one I gave is not what was asked, either, as I misread the question. It was an answer to "which commits are not yet in any tagged version, show them together with the names of branches from which they are reached".

Previous: Johannes SixtNext: Kyle J. McKay
Message 4 of 6 in “git tag --no-merged?”
  1. Peter KreftingFeb 4, 2015
  2. Junio C HamanoFeb 4, 2015
  3. Johannes SixtFeb 4, 2015
  4. Junio C HamanoFeb 4, 2015
  5. Kyle J. McKayFeb 5, 2015
  6. Peter KreftingFeb 5, 2015

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.