All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alexander Mills <alexander.d.mills@gmail.com>
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>, git@vger.kernel.org
Subject: Re: check if one branch contains another branch
Date: Thu, 07 May 2020 16:41:56 -0700	[thread overview]
Message-ID: <xmqqwo5n1fej.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CA+KyZp7Ur3kW3qrCe3hOz16gA9y_B7rSGin62=eKMjCCqLsR4w@mail.gmail.com> (Alexander Mills's message of "Thu, 7 May 2020 16:37:34 -0700")

Alexander Mills <alexander.d.mills@gmail.com> writes:

> I assume that:
>
> git branch -d  xxx
>
> will prevent a delete if the current branch doesn't contain xxx..
> I don't want to have to checkout  origin/dev in order to run that command,
> that's one part of the problem

In that case, don't you want to learn, not just if your 'dev' has
anything that is not merged/accepted by origin/dev, what commits
in 'dev' are not yet merged in origin/dev?

 $ git log origin/dev..dev

would show them.


  reply	other threads:[~2020-05-07 23:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 22:59 check if one branch contains another branch Alexander Mills
2020-05-07 23:08 ` Junio C Hamano
2020-05-07 23:12   ` Alexander Mills
2020-05-07 23:15     ` Alexander Mills
2020-05-07 23:24     ` brian m. carlson
2020-05-07 23:28       ` Alexander Mills
2020-05-07 23:47         ` brian m. carlson
2020-05-07 23:31 ` Randall S. Becker
2020-05-07 23:37   ` Alexander Mills
2020-05-07 23:41     ` Junio C Hamano [this message]
2020-05-08  1:01     ` Alexander Mills
2020-05-08 12:07       ` Randall S. Becker

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=xmqqwo5n1fej.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=alexander.d.mills@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=rsbecker@nexbridge.com \
    /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.