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

Re: feature request: marking a directory as "not meant to be checked out"

From: Kalin KOZHUHAROV <kalin_at_thinrope.net>
Date: 2005-09-22 18:20:09 CEST

Vincent Starre wrote:
> so uh, no interest in this at all? :)
> (usually I at least get "that's a stupid idea" replies...)
Don't top-post :-)

> Vincent Starre wrote:
>> pretty straightforward, an extra property svn:nocheckout (or something
>> better-named) which will, when set on a directory, produce a warning
>> if someone tries to check it out.
>> warning example:
>> svn co svn+ssh://server/ProjectA .
>> svn: The directory "ProjectA" is not meant to be checked out in full.
>> Try "svn ls" to see a list of subdirectories, or use --force to ignore
>> this warning.
>> ideally, a custom warning would be nice, so svn:nocheckout could (in
>> addition to the boolean of being set or not set) contain the warning
>> message (so it can be made to be more informative about what's
>> actually going on)
>> eg:
>> svn co svn+ssh://server/ProjectA .
>> svn: "ProjectA" is just a container. The actual code resides in
>> ProjectA/base, and branches reside in ProjectA/branches.
>> svn: use --force to ignore this warning.

Yes, that is not bad as an idea, but based on the number of responses (excluding self-), it might
not be of top priority to any dev. So unless you have a patch at hand, might not be going anywhere.

It should not be that hard to add one more property, anyway.

Some food for thought:

1. What happens if you have
      | \---trunk
with svn:nocheckout set on prjA and client checkouts projects?

2. <Too tired for 2...sub>


|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 22 18:23:07 2005

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.