From: Junio C Hamano <gitster@pobox•com>
To: Duy Nguyen <pclouds@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: Fwd: Bug#793884: git: allows nonsensical command 'git checkout -b HEAD'
Date: Tue, 28 Jul 2015 09:32:39 -0700 [thread overview]
Message-ID: <xmqqmvygfdjs.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACsJy8Atx7h8LHQ26rTx2jPUxL-+MSLva8njdoUs5+Aq-Eoj4Q@mail.gmail.com> (Duy Nguyen's message of "Tue, 28 Jul 2015 21:33:14 +0700")
Duy Nguyen <pclouds@gmail•com> writes:
> This seems like a good thing to fix (i.e. make sure XX is not
> ambiguous before creating it with "git checkout -b XX")
Yeah, sounds like an easy lunch-time hack low-hanging fruit :-).
prev parent reply other threads:[~2015-07-28 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150728141858.22342.16605.reportbug@zam581.zam.kfa-juelich.de>
2015-07-28 14:33 ` Fwd: Bug#793884: git: allows nonsensical command 'git checkout -b HEAD' Duy Nguyen
2015-07-28 16:32 ` Junio C Hamano [this message]
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=xmqqmvygfdjs.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=pclouds@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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