From: Shourya Shukla <shouryashukla.oo@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, sandals@crustytoothpaste.net
Subject: Re: [PATCH v4 1/4] gitfaq: files in .gitignore are tracked
Date: Sat, 2 May 2020 12:06:24 +0530 [thread overview]
Message-ID: <20200502063624.GC5582@konoha> (raw)
In-Reply-To: <CABPp-BGkZOyyoFiK3hsJ3FQq8MEBPy5aganHjA66vKFE20Wk0Q@mail.gmail.com>
On 29/04 09:16, Elijah Newren wrote:
> Mostly looks good, but I can't help but nitpick several small items:
> The first sentence alone seems to slightly undercut the answer, so
> it'd be nice to make sure the first two sentences are just one. Also,
> it doesn't explain how people get into this state, which is probably
> something users are curious about. The "To ignore and untrack the
> files" lists multiple end results, making it unclear which parts of
> the end results the suggested steps are addressing. There's also a
> "staging are" typo (should be "staging area").
>
> How about something like:
>
> The purpose of gitignore files is to ensure that certain files not
> tracked by Git remain untracked. However, git allows people to
> override the `gitignore` rules by using the --force option to `git
> add`, and sometimes people started tracking a file unintentionally
> before adding a pattern covering it to the gitignore rules. If you
> want to untrack a file, run `git rm --cached <file>` (and then
> commit). See linkgit:gitignore[5] for details.
This seems better, will improve. :)
next prev parent reply other threads:[~2020-05-02 6:36 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 [this message]
2020-04-29 16:55 ` Junio C Hamano
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=20200502063624.GC5582@konoha \
--to=shouryashukla.oo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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).