From: Galder Zamarreno <galder.zamarreno@redhat.com>
To: git@vger.kernel.org
Subject: [egit-jgit] excluded patterns are decorated as being untracked
Date: Tue, 17 Jun 2008 18:43:12 +0200 [thread overview]
Message-ID: <4857E9A0.7070408@redhat.com> (raw)
Hi,
I've been using egit for a few weeks and firstly, I'd like to thank the
people involved in the project for the work done so far.
There's one thing that has been bugging me about egit though which is
related to the decoration of untracked files. Egit/JGit does not seem to
pay attention to .git/info/exclude that I have configured so that
anything under output folder is excluded.
Egit/JGit does seem to have decorations working fine for patterns
specified in "Team/Ignored Resources" but it only applies it to files
not folders, hence, adding "output" as pattern does not work and
instead, I have to specify any pattern that would match a file within
the output folder which is not practical. Folders are taken into account
as ignored resources in subeclipse (subversion eclipse plugin)
I can see two ways of implementing this that I'm happy to have a look
into but I wanted to get some advice from the experts of egit/jgit to
indicate which would be the preferred solution going forward.
1.- Implement .git/info/exclude functionality in egit/jgit
2.- Improve the decoration handling in jgit/egit so that it can check
whether the file is under a pattern that should be excluded. I tried to
implement this but requires using API that eclipse considers internal.
What do people think? Should I bother with 2 or is it better to
implement decorations for patterns in .git/info/exclude correctly?
Thanks!
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
next reply other threads:[~2008-06-17 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 16:43 Galder Zamarreno [this message]
2008-06-17 21:16 ` [egit-jgit] excluded patterns are decorated as being untracked Robin Rosenberg
2008-06-18 4:39 ` Shawn O. Pearce
2008-06-18 15:40 ` Galder Zamarreno
2008-06-18 22:03 ` 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=4857E9A0.7070408@redhat.com \
--to=galder.zamarreno@redhat.com \
--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 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).