From: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic•nl>
To: Robin Rosenberg <robin.rosenberg.lists@dewire•com>
Cc: "Shawn O. Pearce" <spearce@spearce•org>,
"Tor Arne Vestbø" <torarnv@gmail•com>,
"Git Mailing List" <git@vger•kernel.org>
Subject: Re: jgit and ignore
Date: Wed, 04 Mar 2009 18:50:42 +0100 [thread overview]
Message-ID: <49AEBF72.3030901@pelagic.nl> (raw)
In-Reply-To: <200903012124.46600.robin.rosenberg.lists@dewire.com>
Robin Rosenberg wrote:
> Shawn writes:
>> Tor Arne Vestbø <torarnv@gmail•com> wrote:
>>> To me that means that EGit should focus just as much on integrating with
>>> Eclipse properly as it does on keeping command line porcelain
>>> interoperability.
>> Yup, I agree completely. I think Robin would too.
> 100% (or close).
>
Hey guys
I'm currently refactoring the code to accomodate all of your wishes and
I've already come a long way.
==> The one thing that I still need to do is get to the global
core.excludefile setting. How can I do that?
How will it work? Read on... :-)
Suppose we have FILE in DIRECTORY and we want to see whether FILE is
ignored. (FILE can ofcourse also be a DIR)
The way in which ignores will be evaluated is:
1- See if there is a .gitignore file in DIRECTORY. if so, try to match.
when a match is found: FILE is ignored. if there is no .gitignore file or
when no match is found: go one directory up (towards the checkout
root/workdir) and repeat until a match is found or until the .gitignore in
the checkout root/workdir has been evaluated.
2- use the patterns from .git/info/exclude (if exists) and try to match.
when a match is found: FILE is ignored.
3- use the patterns from .git/config:core.excludesfile (when set) and try
to match. when a match is found: FILE is ignored.
4- when .git/config:core.excludesfile was not set, use the patterns from
global:core.excludesfile (when set) and try to match. when a match is
found: FILE is ignored.
5- try to match against the Eclipse global Team ignores. when a match is
found: FILE is ignored.
6- FILE is not ignored
hope this flow is what you want :-)
Ferry
next prev parent reply other threads:[~2009-03-04 17:52 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
2009-03-01 20:24 ` Robin Rosenberg
2009-03-04 17:50 ` Ferry Huberts (Pelagic) [this message]
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=49AEBF72.3030901@pelagic.nl \
--to=ferry.huberts@pelagic$(echo .)nl \
--cc=git@vger$(echo .)kernel.org \
--cc=robin.rosenberg.lists@dewire$(echo .)com \
--cc=spearce@spearce$(echo .)org \
--cc=torarnv@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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