[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:ignore vs. .cvsignore

From: Jason Thaxter <thaxter_at_gmail.com>
Date: 2004-12-08 20:44:35 CET

On 08 Dec 2004 00:44:28 -0600, kfogel@collab.net <kfogel@collab.net> wrote:
> > .svnignore file support solves all disadvantages mentioned above.
> I'm not following this. Could you describe in one sentence an
> 'ignore' feature you get with CVS that you don't get with Subversion?

I can: rsync plays nicely with .cvsignore, and Subversion is not easy
to use this way.

For example, if I have something new to ignore, I could put it into
.cvsignore and I'm done - if I'm using CVS. With Subversion, you have
to add the file to .cvsignore, check it in, then do the propset.
That's two extra, kinda irritating steps.

Of course, this lack could also be regarded as a feature if you
consider that what you want to sync and what you want to version
aren't necessarily the same. And the two extra steps could be
eliminated with a simple wrapper script something like this:
     $EDITOR .cvsignore
     svn propset svn:ignore .
     svn ci -N -m 'updating ignore' . cvsignore

Hmm. I'll have to actually try that. I'm not sure about the -N, which
I've never used. Anyway, sometimes the availability of cheap
workarounds prevents the need for a feature like .svnignore.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 8 20:47:06 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.