From: Jonathan Nieder <jrnieder@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: Johannes Sixt <j6t@kdbg.org>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: enhance gitignore whitelist example
Date: Tue, 5 Apr 2011 16:41:14 -0500 [thread overview]
Message-ID: <20110405214114.GA13729@elie> (raw)
In-Reply-To: <4D9B8862.1050605@redhat.com>
Eric Blake wrote:
> Yeah, but then you have to 'git add -f path/to/file' them every time you
> change them
No, I don't believe that's true.
$ git add -f git.o
$ >git.o
$ git add git.o
.gitignore only protects against starting to track a file that was
previously untracked.
I do tend to use exceptions in .gitignore anyway, since (1) it allows,
as a sanity check,
$ git ls-files -i --exclude-standard
and (2) to import from or compare to a tarball, one can do
$ git rm -rf .
$ git add .
next prev parent reply other threads:[~2011-04-05 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 19:36 [PATCH] Documentation: enhance gitignore whitelist example Eric Blake
2011-04-05 19:40 ` Jonathan Nieder
2011-04-05 21:15 ` Johannes Sixt
2011-04-05 21:23 ` Eric Blake
2011-04-05 21:41 ` Jonathan Nieder [this message]
2011-04-05 21:49 ` Eric Blake
2011-04-05 21:51 ` Junio C Hamano
2011-04-05 21:39 ` Junio C Hamano
2011-04-05 20:56 ` 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=20110405214114.GA13729@elie \
--to=jrnieder@gmail.com \
--cc=eblake@redhat.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
/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).