From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
Cc: "Tor Arne Vestbø" <torarnv@gmail.com>,
"Jon Smirl" <jonsmirl@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: jgit and ignore
Date: Sun, 1 Mar 2009 09:47:29 -0800 [thread overview]
Message-ID: <20090301174729.GC14365@spearce.org> (raw)
In-Reply-To: <49AAC959.70406@pelagic.nl>
"Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl> wrote:
> > IMHO, we should honor ignores in EGit as:
> >
> > per-directory .gitignore
> > per-repostiory GIT_DIR/info/exclude
> >
> > per-repository core.excludesfile (yes, really, it can be per
> > repository, which overrides ~/.gitconfig setting of same)
>
> wow. override? really?
Yes. I'd have to go back and read the git-core code again, but in
general a config setting of foo.bar in GIT_DIR/config overrides a
foo.bar setting in ~/.gitconfig, *unless* you use the --all flag.
Most of the C code parses as though the last value seen is the
only value set, and GIT_DIR/config is parsed after ~/.gitconfig,
hence it overrides.
> > Eclipse global team ignore patterns
>
> so, should these then override, supplement, or something else?
> the per-repo files (.gitignore's and info/exclude supplement eachother.
They all supplement each other. You union every entry in that list
into a single override set and then evaluate against that. That list
changes with each directory, due to the per-directory .gitignore
possibly changing, but otherwise its fixed for any given repository.
--
Shawn.
next prev parent reply other threads:[~2009-03-01 17:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 16:31 jgit and ignore Jon Smirl
2009-02-28 17:26 ` Shawn O. Pearce
2009-03-01 10:11 ` Ferry Huberts (Pelagic)
2009-03-01 12:54 ` Jon Smirl
2009-03-01 13:06 ` Ferry Huberts (Pelagic)
2009-03-01 13:34 ` Tor Arne Vestbø
2009-03-01 13:47 ` Ferry Huberts (Pelagic)
2009-03-01 14:58 ` Tor Arne Vestbø
2009-03-01 17:16 ` Shawn O. Pearce
2009-03-01 17:42 ` Tor Arne Vestbø
2009-03-01 17:49 ` Shawn O. Pearce
2009-03-01 17:51 ` Tor Arne Vestbø
2009-03-01 17:57 ` Shawn O. Pearce
2009-03-01 17:43 ` Ferry Huberts (Pelagic)
2009-03-01 17:47 ` Shawn O. Pearce [this message]
2009-03-01 20:24 ` Robin Rosenberg
2009-03-04 17:50 ` Ferry Huberts (Pelagic)
2009-03-01 17:17 ` Ferry Huberts (Pelagic)
2009-03-01 14:08 ` Jon Smirl
2009-03-01 14:21 ` Tor Arne Vestbø
2009-03-01 14:31 ` Jon Smirl
2009-03-01 14:33 ` Tor Arne Vestbø
2009-03-01 20:47 ` Robin Rosenberg
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=20090301174729.GC14365@spearce.org \
--to=spearce@spearce.org \
--cc=ferry.huberts@pelagic.nl \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=torarnv@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).