Re: [TSVN] NO Bug - Commit with folders over multiple repositories selected

Let's say I have a repository setup like this:
  apps
  + game
    + trunk
  + common

Locally, I have the folders setup like this:
  work
  + game
  + common

If I highlight game and common, and select "SVN Commit" I would expect
the changes in both game and common to be atomically committed. That
is, because they are in the same repository they /can/ get the same
revision number. Tortoise appears to treat this as which file was last
selected rather than the entire selection. In fact, we are being forced
to break the atomicity by having to commit the folders one-by-one.

This is all aside from the multiple repository discussion below. I'd
love to be able to commit over multiple, but I guess a batch file is
going to be the way to go. However I would argue that from a user
interface perspective, having "SVN Update" and "SVN Commit" both
available for single and multiple files does cause confusion.

- Mab

-----Original Message-----
From: SteveKing [mailto:stefankueng@gmail.com]
Sent: Monday, 7 February 2005 7:24 PM
To: dev@tortoisesvn.tigris.org
Subject: Re: [TSVN] NO Bug - Commit with folders over multiple
repositories selected

On Mon, 7 Feb 2005 11:54:36 +1100, Stuart Cameron
<scameron@torus.com.au> wrote:

> We've working with multiple repositories on each of our active
> projects
> - one repository for the cross-project libraries and another for each
> active project. This results in us having multiple URLs from multiple
> repositories checked out to subdirectories of the same folder.
>
> If we select the multiple folders, right click and choose "SVN Commit"
> then we only get a list of changed files for one of the multiple
> selected repositories. Doing an "SVN Update" for multiple selected
> repositories seems to work as expected.

Reason: commits are atomic, updates aren't.

> The behaviour we would expect would be to get a list of all changed
> files across all selected repositories, and for a commit to occur to
> each repository using the same comment. Having to select the folders
> one repository at a time is somewhat error-prone.

No. That would be even worse! Splitting up a commit into several commits
breaks the atomicity of a commit. Also, you can't commit to several
repositories at once, which means they will all get different new
revisions.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org