git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
Cc: Mark Struberg <struberg@yahoo.de>,
	git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: AW: [EGIT] [PATCH RFC v1 5/5] Use the ignore patterns cache to determine ignores
Date: Sun, 3 May 2009 15:17:33 +0200	[thread overview]
Message-ID: <200905031517.33648.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <49FC401A.1030701@pelagic.nl>

lördag 02 maj 2009 14:44:10 skrev "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>:
> Mark Struberg wrote:
> > Ferry,
> > 
> > I was just quickly hacking a rudimentary IgnoreRules class in jgit-core
> > [1] mainly for the purpose of not forgetting about handling ignores
> > finally ;)
> > 
> 
> I think there is no need to do that, I have that in my code already 
> (although in a different form). My implementation reflects what C git does.
> 
> > I now saw you worked on introducing gitignore to EGIT, but wasn't able
> > to find any repo with your code but only a few old patches.
> > 
> 
> it's in my local repo. I have no public repo

Perhaps you could send the patches if they are useful for review. I know Mark is anxious
to get the patch train rolling.

If you do not want us to merge them yet add RFC to the subject prefix, though, I'm pretty sure we 
won't merge the first version anyway...  Big or tricky patch sets rarely pass on the first attempt.

-- robin

  reply	other threads:[~2009-05-03 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-02 11:51 AW: [EGIT] [PATCH RFC v1 5/5] Use the ignore patterns cache to determine ignores Mark Struberg
2009-05-02 12:44 ` Ferry Huberts (Pelagic)
2009-05-03 13:17   ` Robin Rosenberg [this message]
2009-05-03 13:26     ` Ferry Huberts (Pelagic)

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=200905031517.33648.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=ferry.huberts@pelagic.nl \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    --cc=struberg@yahoo.de \
    /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).