From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Elijah Newren <newren@gmail.com>, Git Mailing list <git@vger.kernel.org>
Subject: Re: which files are "known to git"?
Date: Wed, 23 May 2018 04:20:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1805230406050.16917@localhost.localdomain> (raw)
In-Reply-To: <20180521175335.GC10623@aiede.svl.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]
On Mon, 21 May 2018, Jonathan Nieder wrote:
> Robert P. J. Day wrote:
> > On Mon, 21 May 2018, Elijah Newren wrote:
>
> >> Hi Robert,
> >>
> >> I had always assumed prior to your email that 'known to Git'
> >> meant 'tracked' or 'recorded in the index'...
> >
> > i *know* i've been in this discussion before, but i don't
> > remember where, i *assume* it was on this list, and i recall
> > someone (again, don't remember who) who opined that there are two
> > categories of files that are "known to git":
>
> 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.
ironically, the 2nd edition of o'reilly's "version control with git"
uses the phrases "known to Git" and "unknown to Git" on p. 378 (and
nowhere else that i can see):
"Furthermore, for the purposes of this [git clean] command, Git uses a
slightly more conservative concept of under version control.
Specifically, the manual page uses the phrase “files that are unknown
to Git” for a good reason: even files that are mentioned in the
.gitignore and .git/info/exclude files are actually known to Git. They
represent files that are not version controlled, but Git does know
about them. And because those files are called out in the .gitignore
files, they must have some known (to you) behavior that shouldn’t be
disturbed by Git. So Git won’t clean out the ignored files unless you
explicitly request it with the -x option."
that phrase even occurs in git-produced diagnostic messages such as:
dir.c: error("pathspec '%s' did not match any file(s) known to git.",
in any event, perhaps the phrase "known to Git" has some value, as
long as it's defined very precisely and used consistently, which it
obviously isn't right now.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2018-05-23 8:21 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
2018-05-23 8:20 ` Robert P. J. Day [this message]
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=alpine.LFD.2.21.1805230406050.16917@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=newren@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 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).