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

AW: Feature Request: Override auto-prop as project-specific property

From: Schmidt, Maik <Maik.Schmidt_at_mahr.de>
Date: 2006-02-24 08:26:39 CET

Good Morning.

> > Two occuring problems: 1) I check a new file into my small
> project and
> > forget to delete the SVN:needs-lock property before
> commiting. Now I
> > have that property set and have to delete and commit. That is a bit
> > complicated.
> Wrong work flow here: you should not delete the property!
> The svn:needs-lock property indicates that you should get a
> lock first
> before editing. Then when you commit that file, the lock will
> be removed
> (if you don't explicitely tell it not to).

I fear I explained myself the wrong way: I do NOT want to use locking in my small project at all. Since I am the only one working with these source files it is definatelly not necessary. So if I add a new file to the repository, the auto-prop does set the svn:needs-lock even if I do not want it. I have to add the new file, then open the file properties, delete the svn:needs-lock on the TSVN tab and THEN commit the file. My problem is that I often forget to do this and end up with a lock-needing file in my otherwise lock-less project repository. To solve this I have to check out, get the lock, delete the property and commit the file without actualy changing the content.

> > Feature request: It would be nice to have an TSVN-specific
> propery on
> > repository-level which controls if a auto-prop property is
> set or not.
> > Perhaps something like TSVN:SET_THIS_PROP="SVN:needs-lock","*" or
> > something else where TSVN can see what auto-prop it has to
> set for this
> > project only.
> That's a feature request for the Subversion library. This was
> requested
> before (and not for the first or only time), but there never was a
> consensus on *how* to implement this. I guess as soon as that
> happens,
> it won't take long to have this implemented - but the
> consensus is the
> hard part here.

Ah, I understand. I thought that config file was for TSVN to read the values and pass them to the svn functions. I understand now that the SVN library accesses this config file directly? I suppose it is not possible to have that config file as a default and assign a different one to a specific project as an option?

Sincerely and wishing a nice weekend,
Maik Schmidt

P.S.: please cc me

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Feb 24 08:47:15 2006

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

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