Sebastian hi,
Q: ...and what happens if someone want to checkout only a subset of
those projects? A: He will get all of them because of the svn:externals!
Think about it this way:
- somebody wants to delete multiple folders, he selects them and choose
"delete"; if some folder doesn't "delete" then a message is thrown and
the operation stops
- somebody else wants to copy multiple folders, he selects them and
choose "copy" and "paste" them in some other location; if some folder
doesn't "copy/paste" then a message is thrown and the operation stops
- and yet someone else wants to commit multiple working copies, he
selects them and choose "commit"; if some working copy doesn't "commit"
then a message is thrown and the operation stops (the same thing apply
to few other tsvn operations, e.g. "update", "revert" and "clean up")
Adrian.
SebastianUnger@eaton.com wrote:
> - Create yet another repository somewhere (or use one of the existing ones)
> - Create an empty folder in that repository
> - Set svn:externals property on that folder to refer to all projects you want to modify
> - Checkout that folder. That should get all projects required
> - Make mods
> - Commit from top level.
> - As far as I have gathered from comments on the list (I have not tried this myself), this should commit all projects to their respective repositories atomically.
>
> That said, I agree that you probably want to have only one repository with several projects in it. That seems to be the normal setup if projects are related in any way, however distant.
>
> Seb
>
> -----Original Message-----
> From: news [mailto:news@sea.gmane.org]On Behalf Of Adrian Herscu
> Sent: Monday, 25 September 2006 9:21
> To: users@tortoisesvn.tigris.org
> Subject: Re: Commit to multiple repositories
>
>
>
>
> Stefan Küng wrote:
>> Adrian Herscu wrote:
>>> Hi all,
>>>
>>> I have project divided into multiple sub-projects, each one stored in
>>> its own Subversion repository.
>>> Sometimes I am making changes across the project (e.g. changing the
>>> license text, renaming the project, changing the URL to some schema
>>> file, etc.).
>>> Is it possible to commit all sub-projects at once?
>>> I have tried to select all working copies and commit, but TortoiseSVN
>>> commits only the working copy on which the context menu was launched
>>> (not the entire selected set).
>> If you think about it, you would know that it's not possible:
>> Each repository is independent of the others. A commit in Subversion is
>> per definition atomic. But a commit to two (or more) different
>> repositories can't be atomic.
>> You have to commit those changes independently, as are your repositories.
>>
>> Stefan
>>
>
> Why it should not be possible?! I am not asking for atomic
> multi-repository commits!
> Just want to select few working copies and commit them at once, instead
> of clicking four times for each commit.
> Currently I am using a batch script for this, but TortoiseSVN is all
> about GUI, so why not? My batch script is very rudimentary, commits are
> done serially, the reports go to the console, I have to look over to see
> which commit failed...
> Adrian.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Sep 25 08:24:10 2006