Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Subversive » it's too easy to lose history!!!
it's too easy to lose history!!! [message #21492] Thu, 19 June 2008 14:57 Go to next message
Edoardo Comar is currently offline Edoardo ComarFriend
Messages: 102
Registered: July 2009
Senior Member
Deleting a file and adding it back will create a new file - with a
fresh history, example:

in eclipse, take any file (whose history you do not care about) under svn;
using the navigator/project explorer
right click copy and paste (so you have another copy of it)
delete the original
rename the copy as the original
checkin
history is gone

----
I do not know if this is an SVN client bug or an as-designed feature,
however it is very easy to lose the history of a file.


is there a way to restore it ?
or a setting to checkin a file that underwent such lifecycle not as new
but as a new version ?

Edoardo
Re: it's too easy to lose history!!! [message #21507 is a reply to message #21492] Fri, 20 June 2008 03:58 Go to previous messageGo to next message
Francois Cottet is currently offline Francois CottetFriend
Messages: 19
Registered: July 2009
Junior Member
Hi Edoardo,

Yes this behavior is very painful.
I had the same remarks few days ago and it seems to be well-known from
the development team.

One way to avoid this is to do the copy/paste directly in Windows
Explorer or MacOS Finder. If you modify the files and then refresh your
Eclipse view, Subversive will consider the file as 'modified' and not
'replaced'.

Regards,
Francois


Edoardo Comar wrote:
> Deleting a file and adding it back will create a new file - with a fresh
> history, example:
>
> in eclipse, take any file (whose history you do not care about) under svn;
> using the navigator/project explorer
> right click copy and paste (so you have another copy of it)
> delete the original
> rename the copy as the original
> checkin
> history is gone
>
> ----
> I do not know if this is an SVN client bug or an as-designed feature,
> however it is very easy to lose the history of a file.
>
>
> is there a way to restore it ?
> or a setting to checkin a file that underwent such lifecycle not as new
> but as a new version ?
>
> Edoardo
Re: it's too easy to lose history!!! [message #21529 is a reply to message #21507] Fri, 20 June 2008 04:04 Go to previous messageGo to next message
Jörg Thönnes is currently offline Jörg ThönnesFriend
Messages: 229
Registered: July 2009
Senior Member
Hi both,

maybe this is related to my thread "Copy/Past should have svn copy functionality" above.

Cheers, Jörg

On 06/20/08 05:58, Francois Cottet wrote:
> Hi Edoardo,
>
> Yes this behavior is very painful.
> I had the same remarks few days ago and it seems to be well-known from
> the development team.
>
> One way to avoid this is to do the copy/paste directly in Windows
> Explorer or MacOS Finder. If you modify the files and then refresh your
> Eclipse view, Subversive will consider the file as 'modified' and not
> 'replaced'.
>
> Regards,
> Francois
>
>
> Edoardo Comar wrote:
>> Deleting a file and adding it back will create a new file - with a
>> fresh history, example:
>>
>> in eclipse, take any file (whose history you do not care about) under
>> svn;
>> using the navigator/project explorer
>> right click copy and paste (so you have another copy of it)
>> delete the original
>> rename the copy as the original
>> checkin
>> history is gone
>>
>> ----
>> I do not know if this is an SVN client bug or an as-designed feature,
>> however it is very easy to lose the history of a file.
>>
>>
>> is there a way to restore it ?
>> or a setting to checkin a file that underwent such lifecycle not as
>> new but as a new version ?
>>
>> Edoardo
Re: it's too easy to lose history!!! [message #21755 is a reply to message #21529] Fri, 20 June 2008 09:55 Go to previous messageGo to next message
Edoardo Comar is currently offline Edoardo ComarFriend
Messages: 102
Registered: July 2009
Senior Member
I entered
https://bugs.eclipse.org/bugs/show_bug.cgi?id=237899



Jörg Thönnes wrote:
> Hi both,
>
> maybe this is related to my thread "Copy/Past should have svn copy functionality" above.
>
> Cheers, Jörg
>
> On 06/20/08 05:58, Francois Cottet wrote:
>> Hi Edoardo,
>>
>> Yes this behavior is very painful.
>> I had the same remarks few days ago and it seems to be well-known from
>> the development team.
>>
>> One way to avoid this is to do the copy/paste directly in Windows
>> Explorer or MacOS Finder. If you modify the files and then refresh your
>> Eclipse view, Subversive will consider the file as 'modified' and not
>> 'replaced'.
>>
>> Regards,
>> Francois
>>
>>
>> Edoardo Comar wrote:
>>> Deleting a file and adding it back will create a new file - with a
>>> fresh history, example:
>>>
>>> in eclipse, take any file (whose history you do not care about) under
>>> svn;
>>> using the navigator/project explorer
>>> right click copy and paste (so you have another copy of it)
>>> delete the original
>>> rename the copy as the original
>>> checkin
>>> history is gone
>>>
>>> ----
>>> I do not know if this is an SVN client bug or an as-designed feature,
>>> however it is very easy to lose the history of a file.
>>>
>>>
>>> is there a way to restore it ?
>>> or a setting to checkin a file that underwent such lifecycle not as
>>> new but as a new version ?
>>>
>>> Edoardo
Re: it's too easy to lose history!!! [message #21800 is a reply to message #21492] Fri, 20 June 2008 15:18 Go to previous message
Eclipse UserFriend
Originally posted by: alexander.gurov.polarion.org

Hello Edoardo,


This is standard Subversion behaviour: when you manually deleted file then
added a new one Subversion performs a file replacement. Subversive shows
this situation in commit window using "Replaced" status string.
Next moment is that when you perform copy/paste inside Eclipse IDE the
file is deleted by Eclipse first and then copied. Though the Eclipse
behaviour looks strange we can do nothing.

Regarding history loosing - you simply missed one moment :) Yes, replaced
file is a new repository element from the Subversion point of view and
Subversion does not connect it with history of a previous element with the
same name. But Subversion also tracks folder changes. So, you can access
required history by performing few steps:
1) Get the parent folder history
2) Find revision before file replacement
3) Get the history of required file using Affected Paths view.
Previous Topic:svn:needs-lock property?!
Next Topic:Polarion! Broken Update Site and No Access to Working Versions
Goto Forum:
  


Current Time: Sun Dec 21 16:45:59 GMT 2014

Powered by FUDForum. Page generated in 0.02133 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software