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

Re: Check in multiple paths?

From: Dominic Anello <danello_at_danky.com>
Date: 2004-01-09 21:14:56 CET

On 2004-01-09 18:27:20 +0000, Mike Mason wrote:
> Dominic Anello wrote:
> >So is what I am trying to do totally unreasonable, or is it a possible
> >bug?
> >
> >
> I think you need to place all your changes in a single working copy, and
> then commit. Doing a commit across multiple working copies sounds
> difficult (and unnecessary), and not something the Subverion developers
> would be including in a 1.0 release.
> One possible way to achieve this is to commit your changes from each of
> the working copies into a temporary branch, and then merge the branch in
> one go.
> I'm not sure why you're doing this, though...

Because I've been using svn to track my svn configuration. This
necessitated having multiple working copies in different locations. I
know I can copy all the changes into a non disjoint working copy and
commit from there. I was just curious if I had uncovered a bug, since
status had no problem. Also the error message "D: is not a working
copy" was sort of confusing, since not only had I not specified D:\ on
as a target, but D: is a device, not a directory. I guess the code was
looking for a common parent working copy among the paths I specified.

Michael Pilato was kind enough to respond to off-list and indicated that
the capability used to exist, but there was some kind of trade off that
forced it to be removed. It is now post-1.0, apparently.


In the final reckoning there is only love, only that divinity. That we
are capable only of being what we are remains our unforgivable sin.
    -Gene Wolfe
Homepage:    http://danky.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 9 21:11:04 2004

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.