All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
To: "Tor Arne Vestbø" <torarnv@gmail.com>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: jgit and ignore
Date: Sun, 01 Mar 2009 18:17:50 +0100	[thread overview]
Message-ID: <49AAC33E.6030906@pelagic.nl> (raw)
In-Reply-To: <49AAA2B3.40808@gmail.com>

Tor Arne Vestbø wrote:
> Ferry Huberts (Pelagic) wrote:
>> Tor Arne Vestbø wrote:
>>> In my opinion, EGit should default to using Eclipse's built in ignores,
>>> but then detect the presence of a global core.excludesfile, in which
>>> case it would notify the user ("I see you have a core.excludesfile") and
>>> let the user switch to using that one instead.
> 
> [snip]
> 
> First of all, I do appreciate you working on the ignore feature :)
> 
>> I do not agree with your propasal however.
>> We then would have different behaviour between how 'git' behaves within
>> Eclipse (by means of the plugin) and how 'git' behaves within the
>> command line. That alone can cause much more confusion.
> 
> I see what you mean, and I agree that in general the command line git
> porcelain and the Eclipse git porcelain should work in similar ways.
> 
> But, with that said, I think of EGit as a standalone Eclipse-plugin
> implementation of the git porcelain -- not just a wrapper around the
> command line porcelain.
> 
> 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.
> 
> The core.excludesfile is one such case, and I think my proposal is a
> good compromise.
> 

how about we all (especially me) think a bit better on this and solve it
later when I've completed the rest? That allows me to focus for now.
I think we can easily synchronise between the eclipse global ignores and
the core.excludesfile when we (really) want to.

  parent reply	other threads:[~2009-03-01 17:20 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)
2009-03-01 17:17               ` Ferry Huberts (Pelagic) [this message]
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=49AAC33E.6030906@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.