SteveKing wrote:
> Patience, my friend! There's no need to send the message twice in less
> than one hour. We all have jobs and don't have always the time to
> answer right away.
>
Sorry - I thought since I hadn't subscribed yet (an accident on my part)
the initial post wouldn't have gone through.
> So you just select the added file and execute the commit. That's wrong.
> You must select the parent folder for commit - then the commit dialog
> will show you the file with the new name as "added", and the file with
> the old name as "removed". You have then to commit both the added and
> the removed entry.
Ok - what you describe makes sense, even if it's a shame I can't just do
a commit against a file and have it take care of the whole transaction
(I guess then the add would need some sort of flag -- but doesn't it
already have that since the revision history is linked to the old file?).
> Subversion handles renames/moves as a delete and an add, but
> preserving the history. In fact it's a little bit more than a remove
> and an add, because the added file get's an additional entry telling
> Subversion from where it was added (an add of a new file doesn't have
> this).
>
Thanks for the description and help. Again - it makes good common sense.
Maybe subversion's FAQ should have something about doing commit's on
parent folders after a rename. Sure doesn't sound like a Tortoise
issue. *shrug*
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jul 1 20:22:16 2004