New feature: specify history at commit time
From: Pietro Macchi <pietromacchi_at_hotmail.com>
Date: Fri, 2 Aug 2013 07:24:41 -0700 (PDT)
Hi.
The only way I have now to copy a file keeping its SVN "history" is this:
Since this is quite intricate, most of the times I simply skip the SVN part and use LabVIEW only, thus breaking the SVN "history" of the file.
Even if probably this is slightly outside of the way SVN was conceived, I would find very useful the possibility of specifying where an unversioned file "comes from" at commit time, using a drop down menu, for instance.
I add a small example: Let's suppose that I have two files in my repo: document.txt and photo.txt.
If I locally copy document.txt, rename photo.txt and then commit, the commit window will be that of image1.png: the new files are committed as "non-versioned" and photo.txt is committed as missing.
In my dream version there would be the possibility of clicking on the property: "non-versioned" and specify if the new file was actually renamed from a missing file or just copied from another one, which could or not already be in the list (See image2.png).
Another version of this menu could be also added on the status "missing", so that it would be possible to change it to "moved to..." and link it to another file.
I hope it's clear.
Thanks!
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
|
This is an archived mail posted to the TortoiseSVN Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.