From: Christian Jaeger <christian@pflanze.mine.nu>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Erik Hahn <erik_hahn@gmx.de>, git@vger.kernel.org
Subject: Re: Excluding files from git-diff
Date: Fri, 17 Oct 2008 18:30:31 +0200 [thread overview]
Message-ID: <48F8BDA7.50901@pflanze.mine.nu> (raw)
In-Reply-To: <48F8ACC2.1010903@drmicha.warpmail.net>
Michael J Gruber wrote:
> your .gitignore probably doesn't change that often,
> so that it shouldn't show up in the diff after that anyways. Or put it
> in .git/info/excludes.
For me, adding entries to that file does not make "git diff" or "gitk"
or even "git ls-files" ignore files matching the entries. Only "git
ls-files --others --exclude-from=.git/info/exclude" will exclude them.
And "git diff " and gitk don't seem to know the --exclude-from option.
Is there a way to really invert the patterns given to "git diff" or
alike? I.e. instead of saying "git diff -- * .somedotfile
.someothernongitignoredotfile" one could just say something like "git
diff --invert-matches -- .gitignore"? And even better, could one
configure some such so that it has effect on all tools by default?
(That would help working around the clutter problem from the "Separating
generated files?" thread; i.e. in some cases this could be good enough
to not require splitting a project into multiple repositories. (Although
I'm all the same currently working on a
"intergit-find-matching-commit-in" script, since there may be more good
reasons than only the clutter to split projects.))
Christian.
next prev parent reply other threads:[~2008-10-17 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 14:53 Excluding files from git-diff Erik Hahn
2008-10-17 15:08 ` Raphael Zimmerer
2008-10-17 15:08 ` Johannes Schindelin
2008-10-17 15:18 ` Michael J Gruber
2008-10-17 16:30 ` Christian Jaeger [this message]
2008-10-17 17:33 ` Eric Raible
2008-10-18 3:50 ` Christian Jaeger
2008-10-18 15:59 ` Jeff King
2008-10-18 16:08 ` Christian Jaeger
2008-10-18 16:14 ` Jeff King
2008-10-18 16:58 ` Jeff King
2008-10-17 23:38 ` Anders Melchiorsen
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=48F8BDA7.50901@pflanze.mine.nu \
--to=christian@pflanze.mine.nu \
--cc=erik_hahn@gmx.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.