From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Peter Krefting <peter@softwolves.pp.se>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git tag --no-merged?
Date: Wed, 04 Feb 2015 13:27:18 -0800 [thread overview]
Message-ID: <xmqq1tm5nz9l.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <54D26B7C.7020300@kdbg.org> (Johannes Sixt's message of "Wed, 04 Feb 2015 19:57:00 +0100")
Johannes Sixt <j6t@kdbg.org> writes:
> 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".
next prev parent reply other threads:[~2015-02-04 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 15:19 git tag --no-merged? Peter Krefting
2015-02-04 18:43 ` Junio C Hamano
2015-02-04 18:57 ` Johannes Sixt
2015-02-04 21:27 ` Junio C Hamano [this message]
2015-02-05 0:22 ` Kyle J. McKay
2015-02-05 9:09 ` Peter Krefting
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1tm5nz9l.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=peter@softwolves.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.