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

Re: [Subclipse-users] svn:ignore

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-04 19:56:23 CET

David Corbin <dcorbin@machturtle.com> wrote on 03/04/2006 10:25:39 AM:

> I've a svn/rails project, with a partial tree like this:
> project
> vendor
> rails
> plugins
> engines
> login_engine
> vendor has svn:ignore set, yet when I synchonize with subclipse, changes
> in these areas are showing up.

What do you mean it is set? Set to what? svn:ignore does not mean ignore
the item it is set on. Typically a folder would have a property of
svn:ignore with a value of "bin" or "classes", and that would tell
Subversion to ignore the bin or classes folder located beneath the folder
the property is set on.
> login_engine (and maybe rails, I can't remember) are set up as
> "svn:external" (though I can't see it when I do a proplist).

Likewise, if this is an svn:externals then that would mean the property is
set on vendor. Something like:

svn:externals with a value of login_engine url://to/login_engine/project

> reasons, I've essentially got svn projects that are under my main svn
> projects, but they are from another repository, and I don't want to see
> in the synchronize view. svn:ignore doesn't appear to address this. Is

> there another solution?

svn:ignore exists to ignore things you never want in the repository, such
as compiled objects. You can't use it to ignore something that is already
in the repository.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Sat Mar 4 19:56:54 2006

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

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