Re: New feature: specify history at commit time

On 02.08.2013 16:24, Pietro Macchi wrote:
> Hi. I am using TortoiseSVN with LabVIEW. With LabVIEW, you are quite
> forced to use the “save as...” function whenever you want to copy or
> rename a file because otherwise you break inner dependencies and it
> takes quite a lot to fix them. This is not easily usable with
> TortoiseSVN, because also this program needs to be the actual copy
> maker, in order not to break the relationship between the original
> and the copy.
>
> The only way I have now to copy a file keeping its SVN "history" is
> this: 1. Branch the file in the repository with TortoiseSVN. 2.
> Update my working copy. 3. Copy or rename the file with LabVIEW,
> overwriting the file just created by TortoiseSVN.
>
> 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.

First, do not use the dev list for your questions. This is a user
problem and has nothing to do with the development of TSVN.

Second: what you want is already implemented for a long time.
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-rename.html#tsvn-dug-rename-repair

In 1.8 there's also an entry to repair a copy, not just a rename/move.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3061938
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].