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

Re: Committing Checkouts from multiple locations in a single commit.

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-05-05 02:30:18 CEST

On May 4, 2007, at 12:02, Duncan Murdoch wrote:

> On 5/4/2007 12:34 PM, Cuban wrote:
>> How can I commit two seperately checked out folders
>> silmultaneously, so that
>> when viewing the comments in SVN, all the files were commited as
>> the same
>> revision?
>> Here's a diagram of my WORKING Copy configuration:
>> C:\SVN-
>> |_Checkout Folder 1\Files and folders here
>> |_Checkout Folder 2\Files and folders here
>> Both checkout folders are seperate checkouts from different
>> locations in the
>> repository. If I run this command:
>> svn commit "c:\svn" -m "Commited both folders"
>> Only Checkout Folder 1, and all of it's subdirectories/code is
>> commited. - I
>> need checkout 2 subdirectories and code to be committed as well,
>> under the
>> same revision.
> I don't think your description above is correct. If c:\SVN is not
> a working copy, then you would get an error when you tried to
> commit it.

Right, you would have got an error like this:

svn: 'C:\SVN' is not a working copy
svn: Can't open file 'C:\SVN\.svn\entries': No such file or directory

> So I suspect what you really have is your folder 2 checked out into
> the middle of an existing working copy. This can work, but only if
> you define folder 2 as an external of the c:\svn directory. Then
> you could commit changes to both folders in one commit.

But externals aren't a solution either... Subversion will not commit
changes you've made in an external directory if your commit command
is for a directory above the external.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 5 02:31:25 2007

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.