git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Julien Richard via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org, Julien Richard <jairbubbles@hotmail.com>,
	Julien Richard <julien.richard@ubisoft.com>
Subject: Re: [PATCH] doc: 'T' status code for git status
Date: Wed, 09 Dec 2020 16:47:59 -0800	[thread overview]
Message-ID: <xmqqlfe6zdts.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <X9FCUseRteZ1n7ec@coredump.intra.peff.net> (Jeff King's message of "Wed, 9 Dec 2020 16:32:02 -0500")

Jeff King <peff@peff.net> writes:

> TBH, I find the whole table overly confusing. But then, I am completely
> comfortable with the notion that it is really showing two diffs, with
> their results collated. To me it is simpler to just discuss the two
> sides of the diff independently, and then you do not even really need a
> table at all ("M" means modified no matter which column it appears in).
> But I may not be a representative Git user.

Me neither.  I think the folks who originally wanted to see the
table was curious about what combination of X and Y are possible.

For example, if a path is deleted in the index, there won't be any
intelligent thing we can say about the path in the working tree, so
after "git rm COPYING" we'd see "D COPYING", not "DD COPYING", and
after "git rm --cached COPYING && date >COPYING", we'd still see "D
COPYING", not "DM COPYING".

It is unclear how such knowledge would be useful to the readers, so
I won't shed tears if we got rid of the table; the bits saved might
be better used to enhance the description in the list of mnemonics.

Thanks.


  reply	other threads:[~2020-12-10  0:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  8:13 [PATCH] doc: 'T' status code for git status Julien Richard via GitGitGadget
2020-12-09 17:37 ` Jeff King
2020-12-09 18:01   ` Julien Richard
2020-12-09 18:35     ` Jeff King
2020-12-09 20:26   ` Junio C Hamano
2020-12-09 20:56     ` Julien Richard
2020-12-09 21:32     ` Jeff King
2020-12-10  0:47       ` Junio C Hamano [this message]
2020-12-09 19:12 ` [PATCH v2] " Julien Richard via GitGitGadget

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqlfe6zdts.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=jairbubbles@hotmail.com \
    --cc=julien.richard@ubisoft.com \
    --cc=peff@peff.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).