RE: Re: Feature Request: Dual-Commit

That's exactly why I said that TSvn might have to just perform the current process behind the scenes. Either way, it'd make it easier for users. It's been 8 years since I've worked in C++, so I have very little interest in jumping into it for something like this. I merely wanted to throw my 2 cents out there.

Michael

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Monday, December 19, 2005 2:50 PM
To: dev@tortoisesvn.tigris.org
Subject: Re: Feature Request: Dual-Commit

Flanakin Michael C Ctr HQ OSSG/OMR wrote:
> Occasionally, when I'm working on a fix in a branch, I want to commit
> that fix to both the branch and the trunk. Currently, I have to commit
> to branch, switch to trunk, merge the two, commit the trunk, and
> switch back to the branch. That's a lot of work just to commit what
> I've got to two places. Granted, this only happens when I know that
> both files are the same. Actually, in most of my cases, I tend to be
> in the trunk when I'm fixing it and commit just that change to the trunk and branch.
>
> I know the prospective risk that is being taken is that one might
> commit more than the desired change; but that can happen any number of
> ways if someone's not paying attention, so I don't think that's a very
> good argument against this capability.
>
> Anyway, what're the chances of adding something like this to TSvn? I
> know there's nothing that Svn has like this, but it can be mocked up
> pretty easily. For instance, have a checkbox and textbox to specify
> whether to do a dual-commit as well as a secondary URL. Behind the
> scenes, there are simply two commits that take place (actually, I may
> be wrong; you may have to complete the previously mentioned process).
> There could be a few other things added later to help resolve issues
> that may come up from this (i.e. compare and maybe only allow
> dual-commits for files of the same repository version).

Comments like "can be mocked up pretty easily" always make me feel bad.
If it is that easy, why do you request the feature and don't implement it yourself and send a patch?

That said: you haven't really thought about how Subversion works. What you're requesting isn't possible.

You want to commit to a branch for which you don't have a working copy for. Without a working copy, Subversion can't know if you're up-to-date with the repository. So a commit is not possible. Your request would be "overwrite files in the repository without me knowing what exactly I'm overwriting" - Subversion doesn't do that. Neither officially nor with tricks or cheating - it's not possible.

If you really want such a feature, you have to implement something like this yourself in the Subversion library.

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