From: Junio C Hamano <gitster@pobox.com>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: git@vger.kernel.org, sandals@crustytoothpaste.net
Subject: Re: [PATCH v3 1/4] gitfaq: files in .gitignore are tracked
Date: Tue, 21 Apr 2020 12:45:47 -0700 [thread overview]
Message-ID: <xmqq7dy8oc5w.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200421131223.29337-2-shouryashukla.oo@gmail.com> (Shourya Shukla's message of "Tue, 21 Apr 2020 18:42:20 +0530")
Shourya Shukla <shouryashukla.oo@gmail.com> writes:
> Add issue in 'Common Issues' section which addresses the problem of
> Git tracking files/paths mentioned in '.gitignore'.
I do not think this much text is warranted in this file.
The first part of Documentation/gitignore.txt *ought* to cover this
material and it does say "specifies intentionally untracked files"
and "already tracked byt Git are not affected". Read that paragarph
twice, and then jump to the NOTES section it refers two and also
read that twice. Then let's work on polishing these places if there
is anything unclear. I think what we have there is clear enough.
And then trim the text we see here down. The way the question is
phrased may be good as-is (I trust that you researched to make sure
that is how the question is most frequently phrased). The answer
should be just "see gitignore(5)", or perhaps repeat the first
paragraph of gitignore(5) and then refer to the page, i.e. no more
than
[[files-in-.gitignore-are-tracked]]
I asked Git to ignore various files, yet they are still tracked::
A `gitignore` file specifies intentionally untracked files
that Git should ignore. Files already tracked by Git are
not affected. See linkgit:gitignore[5] for details.
should be in the FAQ file.
next prev parent reply other threads:[~2020-04-21 19:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 13:12 [PATCH v3 0/4] gitfaq: add issues in the 'Common Issues' section Shourya Shukla
2020-04-21 13:12 ` [PATCH v3 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
2020-04-21 19:45 ` Junio C Hamano [this message]
2020-04-21 13:12 ` [PATCH v3 2/4] gitfaq: changing the remote of a repository Shourya Shukla
2020-04-21 19:54 ` Junio C Hamano
2020-04-27 17:30 ` Shourya Shukla
2020-04-21 13:12 ` [PATCH v3 3/4] gitfaq: shallow cloning " Shourya Shukla
2020-04-21 20:00 ` Junio C Hamano
2020-04-21 20:43 ` Randall S. Becker
2020-04-21 20:57 ` Junio C Hamano
2020-04-21 21:25 ` Randall S. Becker
2020-04-22 1:30 ` Derrick Stolee
2020-04-22 4:00 ` Jonathan Nieder
2020-04-22 0:13 ` Elijah Newren
2020-04-21 13:12 ` [PATCH v3 4/4] gitfaq: fetching and pulling " Shourya Shukla
-- strict thread matches above, loose matches on Subject: below --
2020-04-21 13:11 [PATCH v3 0/4] gitfaq: add issues in the 'Common Issues' section Shourya Shukla
2020-04-21 13:11 ` [PATCH v3 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
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=xmqq7dy8oc5w.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=shouryashukla.oo@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).