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

RE: Re: Best Practice for Ignoring Files

From: Peter Mounce <Peter.Mounce_at_whitbybird.com>
Date: 2006-05-31 17:05:43 CEST

> From: news [mailto:news@sea.gmane.org] On Behalf Of Kevin Cannon
> Peter Mounce <Peter.Mounce@...> writes:
> > I have "_notes" as one line of my svn:ignore, which I maintain
> > recursively through my WCs. That is, if my tree grows, I
> re-propagate
> > svn:ignore recursively from the root of the WC. This works.
> Hi Peter, thanks for the reply.
> I forgot to mention I'm a designer, so I'm not too familiar
> with how subversion works in detail. Though I'm willing to
> learn, but go easy on me. :)

You're using Dreamweaver; I'd made the logical leap ;-)
> I have a few questions.
> Where do you have the svn:ignore set exactly?

I've attached a text file containing my standard setting. Each entry in
svn:ignore goes on its own line.

> What does WC stand for?

"Working Copy".

> Do you still get prompted with the _notes directories when committing?

No. But remember you need to commit changes to properties too - they
count as changes to files, and are versioned. And when you add more
directories, they don't automatically get the properties of the parent
directory until and unless you re-set the properties (either recursively
on a higher directory than the new one, or specifically on the new one).

Most of this is in the (excellent, easily searchable) manual that ships
with TortoiseSVN, or in the svnbook which is available online - google
svnbook and it's the first hit, usually. Hell, google for svn:ignore
and you'll get lots of useful hits, since the mailing lists are indexed.


To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org

Received on Wed May 31 17:05:55 2006

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

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