From: Junio C Hamano <gitster@pobox.com>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: git@vger.kernel.org, newren@gmail.com, sandals@crustytoothpaste.net
Subject: Re: [PATCH v4 1/4] gitfaq: files in .gitignore are tracked
Date: Wed, 29 Apr 2020 09:55:35 -0700 [thread overview]
Message-ID: <xmqqimhixmd4.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200429093811.8475-1-shouryashukla.oo@gmail.com> (Shourya Shukla's message of "Wed, 29 Apr 2020 15:08:08 +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'.
>
> Signed-off-by: Shourya Shukla <shouryashukla.oo@gmail.com>
> ---
> Documentation/gitfaq.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/gitfaq.txt b/Documentation/gitfaq.txt
> index 1cf83df118..b1e758ffd1 100644
> --- a/Documentation/gitfaq.txt
> +++ b/Documentation/gitfaq.txt
> @@ -223,6 +223,15 @@ a file checked into the repository which is a template or set of defaults which
> can then be copied alongside and modified as appropriate. This second, modified
> file is usually ignored to prevent accidentally committing it.
>
> +[[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.
> + To ignore and untrack the files appearing in the staging are
> + it is advised to use `git rm --cached <file>`as well as make
> + the file pattern is mentioned in the '.gitignore'.
After trimming down, it got a lot more readable. The last sentence
is not quite, though, with riddled with typos. Also the order of
untrack/ignore and steps to achieve these two things should match in
the description.
To untrack and ignore files, use `git rm --cached <file>`
and add a pattern to `.gitignore` that matches the <file>.
may be the minimum fix.
Thanks.
prev parent reply other threads:[~2020-04-29 16:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 9:38 [PATCH v4 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
2020-04-29 9:38 ` [PATCH v4 2/4] gitfaq: changing the remote of a repository Shourya Shukla
2020-04-29 16:17 ` Elijah Newren
2020-04-29 17:01 ` Junio C Hamano
2020-04-29 9:38 ` [PATCH v4 3/4] gitfaq: shallow cloning " Shourya Shukla
2020-04-29 16:00 ` Elijah Newren
2020-05-02 5:00 ` Shourya Shukla
2020-04-29 17:09 ` Junio C Hamano
2020-05-02 6:13 ` Shourya Shukla
2020-05-04 16:06 ` Junio C Hamano
2020-05-05 12:26 ` Derrick Stolee
2021-05-06 2:49 ` dyrone teng
2020-04-29 9:38 ` [PATCH v4 4/4] gitfaq: fetching and pulling " Shourya Shukla
2020-04-29 15:56 ` Elijah Newren
2020-04-29 17:19 ` Junio C Hamano
2020-05-02 6:57 ` Shourya Shukla
2020-05-02 19:00 ` Elijah Newren
2020-05-03 1:03 ` Junio C Hamano
2020-04-29 16:16 ` [PATCH v4 1/4] gitfaq: files in .gitignore are tracked Elijah Newren
2020-05-02 6:36 ` Shourya Shukla
2020-04-29 16:55 ` Junio C Hamano [this message]
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=xmqqimhixmd4.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--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.
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).