From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: which files are "known to git"?
Date: Mon, 21 May 2018 11:53:56 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1805211151360.17797@localhost.localdomain> (raw)
In-Reply-To: <CABPp-BH0bw3m5Ubz2+-XyFGwoHD96sAaSen9-SHQSBqMS-9u5w@mail.gmail.com>
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'. However, a quick `git grep -i
> known.to.git` shows that we're actually not consistent by what we
> mean with this phrase. A little test setup:
>
> $ echo ignoreme >>.gitignore
> $ git add .gitignore
> $ git commit -m ignoreme
> $ touch ignoreme
> $ git ls-files -o
> ignoreme
> $ git ls-files -o --exclude-standard
> $
>
> >From Documentation/git-clean.txt:
>
> Normally, only files unknown to Git are removed, but if the `-x`
> option is specified, ignored files are also removed.
>
> This implies that ignored files are not 'unknown to Git', or fixing the
> double negative, that ignored files are 'known to Git':
> $ git clean -n
> $ git clean -nx
> Would remove ignoreme
> $
uh oh ... i'm just now remembering a discussion once upon a time
where this wasn't simply a double negative. IIRC (and someone else
help me out here), "known to git" also meant known *not* to be tracked
or something like that (as in, ignored files).
anyone remember that conversation?
rday
next prev parent reply other threads:[~2018-05-21 15:55 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 [this message]
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
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
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=alpine.LFD.2.21.1805211151360.17797@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--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.
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).