From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>,
Michael J Gruber <git@drmicha.warpmail.net>,
Thomas Rast <trast@student.ethz.ch>
Subject: Re: [PATCH] reset: update help text
Date: Thu, 31 Mar 2011 16:57:41 -0500 [thread overview]
Message-ID: <20110331215741.GA20474@elie> (raw)
In-Reply-To: <7v39m3j780.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>> [1] Detailed semantics: for each path listed by "git diff --name-only
>> HEAD <commit>":
>>
>> * if the worktree, index, and HEAD match, make the index and worktree
>> match <commit>.
>>
>> * otherwise, if it is "not easy" to keep local changes, error out.
>> We are not going to do a three-way merge. That is,
>>
>> - if the index matches neither HEAD nor <commit>, error out;
>> - if the index matches HEAD but not the worktree, error out.
>>
>> * otherwise, it is "easy", so keep local changes.
>>
>> - if the index already matches <commit>, leave the index and
>> worktree alone.
>> - if the index and worktree match HEAD, make them match the
>> <commit> instead.
>
> The latter item in the last "otherwise" is the same as the first "if all
> match, move to the one from the named commit", isn't it?
Yes, sorry for the nonsense.
next prev parent reply other threads:[~2011-03-31 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 13:20 [PATCH] reset: update help text Nguyễn Thái Ngọc Duy
2011-03-29 13:29 ` Nguyen Thai Ngoc Duy
2011-03-29 21:04 ` Jonathan Nieder
2011-03-31 12:31 ` Nguyen Thai Ngoc Duy
2011-03-31 18:42 ` Jonathan Nieder
2011-03-31 21:44 ` Junio C Hamano
2011-03-31 21:57 ` Jonathan Nieder [this message]
2011-04-02 8:43 ` Nguyen Thai Ngoc Duy
2011-03-31 18:45 ` 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=20110331215741.GA20474@elie \
--to=jrnieder@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=trast@student.ethz.ch \
/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).