git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: Alex Blewitt <alex@bandlem.com>,
	Francis Galiegue <fge@one2team.com>,
	git@vger.kernel.org, spearce@spearce.org
Subject: Re: [EGit PATCH] IgnoreAction to add to .gitignore files
Date: Thu, 23 Apr 2009 22:17:56 +0200	[thread overview]
Message-ID: <49F0CCF4.20808@pelagic.nl> (raw)
In-Reply-To: <200904232119.36707.robin.rosenberg@dewire.com>

Robin Rosenberg wrote:
> torsdag 23 april 2009 14:32:46 skrev Alex Blewitt <alex@bandlem.com>:
>> Actually, that's pretty much exactly the format that Eclipse users  
>> will be expecting.
>>
>> CVS: Add to .cvsignore
>> SVN: Add to svn:ignore
>>
>> I suggest that we go with that style of format for the menu items, in  
>> order to achieve consistency with the way that the other team  
>> providers work.
> 
> Ouch, top posting....
> 
> Anyway, I agree  with Alex. My motivation is that there are more
> than one way to specify ignore. There's .gitignore, .git/info/excludedes
> and the Team ignore settings themselves. This option specifically
> messes with .gitignore. 
> 
while we're on the subject...
how about also adding the reverse: when a file is ignored then add it to
the .gitignore file for 'un-ignoring' (the '!' pattern)

  reply	other threads:[~2009-04-23 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 11:50 [EGit PATCH] IgnoreAction to add to .gitignore files Alex Blewitt
2009-04-23 12:27 ` Francis Galiegue
2009-04-23 12:32   ` Alex Blewitt
2009-04-23 19:19     ` Robin Rosenberg
2009-04-23 20:17       ` Ferry Huberts (Pelagic) [this message]
2009-04-23 20:26         ` Robin Rosenberg
2009-04-23 20:36           ` Alex Blewitt
2009-04-23 20:48             ` Ferry Huberts (Pelagic)
2009-04-23 21:09             ` Robin Rosenberg
2009-04-23 21:12               ` Alex Blewitt
2009-04-23 23:08                 ` 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=49F0CCF4.20808@pelagic.nl \
    --to=ferry.huberts@pelagic.nl \
    --cc=alex@bandlem.com \
    --cc=fge@one2team.com \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg@dewire.com \
    --cc=spearce@spearce.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).