git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH RESEND] git gui: make current branch default in "remote delete branch" merge check
Date: Sat, 05 Dec 2009 14:19:53 +0100	[thread overview]
Message-ID: <4B1A5DF9.70203@web.de> (raw)
In-Reply-To: <20091204212648.GA3979@book.hvoigt.net>

Heiko Voigt schrieb:
> We already do the same when locally deleting a branch.

+1

This is very useful in a workflow where the reviewer deletes the remote
feature branch right after merging and pushing it.


Jens

  reply	other threads:[~2009-12-05 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 21:26 [PATCH RESEND] git gui: make current branch default in "remote delete branch" merge check Heiko Voigt
2009-12-05 13:19 ` Jens Lehmann [this message]
2009-12-05 21:18 ` Shawn O. Pearce
  -- strict thread matches above, loose matches on Subject: below --
2009-09-20  9:47 Heiko Voigt

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=4B1A5DF9.70203@web.de \
    --to=jens.lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hvoigt@hvoigt.net \
    --cc=spearce@spearce.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).