From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2016, #05; Mon, 19)
Date: Wed, 21 Sep 2016 08:44:45 -0700 [thread overview]
Message-ID: <xmqq4m59cl5e.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CACsJy8Dwe1n-YQfNMOyduLksNhAkAEPpBE3S0n==T-D1E0BneA@mail.gmail.com> (Duy Nguyen's message of "Wed, 21 Sep 2016 16:11:00 +0700")
Duy Nguyen <pclouds@gmail.com> writes:
> On Tue, Sep 20, 2016 at 6:30 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> * nd/checkout-disambiguation (2016-09-09) 4 commits
>> - fixup! checkout.txt: document a common case that ignores ambiguation rules
>> - checkout: fix ambiguity check in subdir
>> - checkout.txt: document a common case that ignores ambiguation rules
>> - checkout: add some spaces between code and comment
>>
>> "git checkout <word>" does not follow the usual disambiguation
>> rules when the <word> can be both a rev and a path, to allow
>> checking out a branch 'foo' in a project that happens to have a
>> file 'foo' in the working tree without having to disambiguate.
>> This was poorly documented and the check was incorrect when the
>> command was run from a subdirectory.
>>
>> Waiting for an Ack for fixup!
>
> Oops, I didn't know (I have about 300 unread git mails in my inbox), Ack.
Thanks.
next prev parent reply other threads:[~2016-09-21 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 23:30 What's cooking in git.git (Sep 2016, #05; Mon, 19) Junio C Hamano
2016-09-20 21:50 ` Johannes Schindelin
2016-09-21 15:40 ` Junio C Hamano
2016-09-21 18:22 ` Johannes Schindelin
2016-09-21 9:11 ` Duy Nguyen
2016-09-21 15:44 ` Junio C Hamano [this message]
2016-09-21 16:26 ` Kevin Daudt
2016-09-21 17:36 ` Junio C Hamano
2016-09-21 17:45 ` Kevin Daudt
2016-09-22 6:49 ` Jeff King
2016-09-22 22:14 ` 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=xmqq4m59cl5e.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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.