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

should I raise an issue? commit multiple dirs without parent WC

From: Dave Rodgman <dave.rodgman_at_arm.com>
Date: 2005-08-15 14:40:51 CEST


as previously discussed, the subversion commandline client won't commit
multiple directories [from a single repository], unless they have a
parent directory which is a working copy. Under the right circumstances,
it seems to work if the parent is any arbitrary directory, but arranging
the working copy this way starts becoming awkward.

Given that a common subversion repository layout (at least round here)


people often checkout module1/trunk as module1; given that people
usually want to work with a set of modules from a single branch, this
seems like a reasonable thing to do. For projects imported from CVS,
this is necessary from a build point of view, since this is the same
structure created by CVS - this is a big issue for us.

Anyway, the upshot is that people often want to do

svn ci module1 module2

but can't.

Should I raise an issue about this? I couldn't find one in the issue
tracker. It might seem trivial but in some ways seems to undermine the
very nice "atomic commits" property that subversion provides.

Previous discussion at:

http://www.chiark.greenend.org.uk/~sgtatham/svn.html (section 7.4,
discusses work-around)



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 15 14:41:31 2005

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

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