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).
>
> Personally, I know I would benefit from this feature. I imagine others
> would, too.
>
> Michael Flanakin
>
Why stop at dual?
Probably more a question for the Subversion dev list but I don't like
your chances.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Dec 19 20:15:36 2005