[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Rename in Subversion

From: Srilakshmanan, Lakshman <lakshman.srilakshmanan_at_police.vic.gov.au>
Date: 2007-12-21 00:07:30 CET

Hi All,

Thanks for this discussion.

John,

> He needs to checkin the containing directory
I believe I said this in my original email as a work around (see below).

> The new file still has all of the history of the previous file...
This is correct, but the old file does not have the history anymore :(

As Andy said :
> Right but if he's only committing the "new" file, TSVN won't commit
the delete, because > it isn't connected to that file.

I would have expected the user to be able to commit the renamed file
(new file) and for all associated schedules to form part of that
transaction, or am I asking for too much :)

Ryan,

> I have no information on this "object ID" notion however.
http://svn.haxx.se/users/archive-2007-12/0462.shtml

Lakshman said :

> We cannot commit the original file delete operation because the file
does not exist.
> The only way around is to commit the entire directory (and uncheck the
files you don't
> want to commit, if you are using a GUI client like TortoiseSVN).

The issue in leaving the rename process "as is" will affect the **
command-line ** users as there is no way to commit the rename without
committing the entire directory (which may contain other changes).

So, the question is, should we leave it "as is" or report it as a
required improvement ?

Thanks
Lakshman
-----Original Message-----
From: John Peacock [mailto:john.peacock@havurah-software.org]
Sent: Friday, 21 December 2007 1:59 AM
To: Andy Levy
Cc: Srilakshmanan, Lakshman; users@subversion.tigris.org
Subject: Re: Rename in Subversion

Andy Levy wrote:
> Right but if he's only committing the "new" file, TSVN won't commit
> the delete, because it isn't connected to that file.

Yup, I just recreated that behavior. He needs to checkin the containing
directory (which should still have the scheduled delete waiting). It's
going to mess up the history a little because the add+history and delete
didn't happen in the same revision, but it is harmless. The new file
still has all of the history of the previous file...

John

================================================================================================
EMAIL DISCLAIMER

This email and any attachments are confidential. They may also be subject to copyright.

If you are not an intended recipient of this email please immediately contact us by replying
to this email and then delete this email.

You must not read, use, copy, retain, forward or disclose this email or any attachment.

We do not accept any liability arising from or in connection with unauthorised use or disclosure
of the information contained in this email or any attachment.

We make reasonable efforts to protect against computer viruses but we do not accept liability
for any liability, loss or damage caused by any computer virus contained in this email.
================================================================================================

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 21 00:07:26 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.