From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Elijah Newren <newren@gmail.com>,
Git Mailing list <git@vger.kernel.org>
Subject: Re: which files are "known to git"?
Date: Tue, 22 May 2018 11:14:31 +0900 [thread overview]
Message-ID: <xmqqefi4zbaw.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180521175335.GC10623@aiede.svl.corp.google.com> (Jonathan Nieder's message of "Mon, 21 May 2018 10:53:35 -0700")
Jonathan Nieder <jrnieder@gmail.com> writes:
> My understanding was the same as Elijah's.
>
> I would be in favor of a patch that replaces the phrase "known to Git"
> in Git's documentation with something less confusing.
One possible twist I recall was that normally we only pay attention
to the index (i.e. the term "tracked files" means "paths shown in
ls-files (no args) output"), but there was a desire to take a union
of paths in the index and paths in the HEAD (the obvious difference
is those that are removed from the index), and we may have called
these "known to Git" in the discussion to distinguish them from
"paths in the index".
Clearly the phrase we are discussing (e.g. the ones used in "git
clean" documentation) has been used _without_ such a desire but
merely is used carelessly and confusingly. So I am all for finding
"known to Git" and replace them with "tracked" and/or "added to the
index" when the phrase is not used to mean "union of paths in the
index and in the HEAD".
Thanks.
next prev parent reply other threads:[~2018-05-22 2:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 11:18 which files are "known to git"? Robert P. J. Day
2018-05-21 13:58 ` Randall S. Becker
2018-05-21 15:09 ` Elijah Newren
2018-05-21 15:18 ` Duy Nguyen
2018-05-21 15:49 ` Robert P. J. Day
2018-05-21 15:53 ` Robert P. J. Day
2018-05-21 16:08 ` Junio C Hamano
2018-05-21 17:40 ` Robert P. J. Day
2018-05-21 17:53 ` Jonathan Nieder
2018-05-21 18:09 ` Robert P. J. Day
2018-05-21 18:15 ` Jonathan Nieder
2018-05-22 2:14 ` Junio C Hamano [this message]
2018-05-23 8:20 ` Robert P. J. Day
2018-05-21 18:13 ` Elijah Newren
2018-05-21 18:14 ` Robert P. J. Day
2018-05-21 18:15 ` Stefan Beller
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=xmqqefi4zbaw.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=newren@gmail.com \
--cc=rpjday@crashcourse.ca \
/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).