From: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
To: "Shawn O. Pearce" <spearce@spearce.org>
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, 01 Mar 2009 18:43:53 +0100 [thread overview]
Message-ID: <49AAC959.70406@pelagic.nl> (raw)
In-Reply-To: <20090301171648.GB14365@spearce.org>
> 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?
>
> 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.
> Skipping the core.excludesfile in favor of only the Eclipse global
> team ignores feels wrong to me, as we may be missing something
> the user has configured. FWIW, I think core.excludesfile is a
> lot less frequently used then .gitignore and GIT_DIR/info/exclude.
> If there is a core.excludesfile, the user is a pretty advanced user
> and they really want that behavior to be honored by Git poreclain.
> EGit should honor it.
I could also argue that an advanced user would expect Egit and git to
behave the same. especially for advanced features. and even more so
because EGit now is very basic and to be able to use the advanced
features you have to switch to the commandline from Eclipse. making this
a very very real use-case for EGit usage.
Once we have more advanced features implemented this use-case will
become less prevalent and only then I'd (personally) be more inclined to
allow more behaviour differences
next prev parent reply other threads:[~2009-03-01 17:45 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) [this message]
2009-03-01 17:47 ` Shawn O. Pearce
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=49AAC959.70406@pelagic.nl \
--to=ferry.huberts@pelagic.nl \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=spearce@spearce.org \
--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).