From: Junio C Hamano <gitster@pobox.com>
To: Mark Dominus <mjd@icgroup.com>
Cc: git@vger.kernel.org, Mark Dominus <mjd@plover.com>
Subject: Re: [PATCH] document 'T' status from git-status
Date: Sun, 30 Oct 2011 21:18:19 -0700 [thread overview]
Message-ID: <7vpqhdrdys.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4EADB4DB.5020004@icgroup.com> (Mark Dominus's message of "Sun, 30 Oct 2011 16:34:35 -0400")
Mark Dominus <mjd@icgroup.com> writes:
>> The current organization of this table may need to be rethought, but if we
>> were to keep it, then this change is far from sufficient. For example, you
>> do not explain what XY = TT means.
> Thanks for your response.
>
> I did not try to document that because in my experimenting I was not
> able to produce that situation.
It is trivial if you realize that X is the change between the HEAD and the
index, and Y is the change between the index and the working tree. Most
importantly, no direct comparison between the HEAD and the working tree
gets in the picture.
$ mv COPYING RENAMING
$ ln -s RENAMING COPYING
$ git add COPYING
$ mv RENAMING COPYING
$ git status -suno
TT COPYING
> Will you be applying the alternative patch you suggested, or would you
> prefer that I try to produce one along those lines?
I dunno.
An obvious alternative is to add T next to all occurrences of M in the
table where we say "M is possible", but unless it is accompanied by an
explanation "T is just a special case of M", I suspect the resulting
description would be harder to understand than currently is, and as long
as the reader understands "T is just a special case of M", then there
isn't much point adding T everywhere M appears in the table anyway, so...
next prev parent reply other threads:[~2011-10-31 4:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 0:06 [PATCH] document 'T' status from git-status Mark Dominus
2011-10-30 6:25 ` Junio C Hamano
2011-10-30 20:34 ` Mark Dominus
2011-10-31 4:18 ` Junio C Hamano [this message]
2011-10-31 14:04 ` Mark Dominus
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=7vpqhdrdys.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mjd@icgroup.com \
--cc=mjd@plover.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 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).