[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: David Corbin <dcorbin_at_machturtle.com>
Date: 2006-03-05 00:04:15 CET

On Saturday 04 March 2006 01:56 pm, Mark Phippard wrote:
> 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
> made
> > 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.

I've figured out part of what I was doing wrong. I was doing a proplist when
I needed to do
a propget.

> > 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

I'm sure login_engine was set up as an svn:external, but I proplist is not
showing it to me.

> > 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
> them
> > 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.

Is there subclipse feature for 'hiding' a branch? I've essentially got
multiple projects in one tree (not the way I want to do things, but it's the
rails way, and woe unto he who doesn't follow rails conventions:) ), but I
really only want to manage one (the root) through subclipse. I wouldn't even
have the others under it, but I have to create a patch, and for whomever to
release a version with that patch, before I can just eliminate it.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sun Mar 5 00:05:49 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.