All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
	"Conrad Irwin" <conrad.irwin@gmail.com>,
	"☂Josh Chia (谢任中)" <joshchia@gmail.com>,
	git@vger.kernel.org, "Soeren Sonnenburg" <sonne@debian.org>
Subject: Re: git branch -M" regression in 1.7.7?
Date: Sun, 27 Nov 2011 00:09:21 +0100	[thread overview]
Message-ID: <m2bory5vmm.fsf@igel.home> (raw)
In-Reply-To: <7v39day0fb.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sat, 26 Nov 2011 14:38:16 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> I havn't look at the patch (not a regression between 1.7.7 and 1.7.8 so
> not a candidate for the remainder of this cycle), but I like the above
> description quite a lot. I think Linus's "git reset --sane" which was
> initially called "git reset --merge" but ended up as "git reset --keep"
> should have been spelled as "checkout -B <current-branch>" from the
> beginning.

It is more convenient if you don't have to spell out the name of the
current branch (which fails if you aren't on a branch).

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2011-11-26 23:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26  0:36 git branch -M" regression in 1.7.7? ☂Josh Chia (谢任中)
2011-11-26  2:30 ` Jonathan Nieder
2011-11-26  6:52   ` [PATCH] Test renaming a branch to itself Conrad Irwin
2011-11-26  6:59     ` Jonathan Nieder
2011-11-26  7:05   ` git branch -M" regression in 1.7.7? Conrad Irwin
2011-11-26  8:54     ` Jonathan Nieder
2011-11-26 22:38       ` Junio C Hamano
2011-11-26 23:09         ` Andreas Schwab [this message]
2011-11-28 19:38   ` Junio C Hamano

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=m2bory5vmm.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=conrad.irwin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=joshchia@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=sonne@debian.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 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.