On Thu, Jul 17, 2014 at 6:03 AM, Daniel Migowski wrote:
> Hello,
>
> I have to say sorry for the noise. You were right, after retrying to cleanup
> my old copies of the working copy it occurred to me that subversion really
> can clean things up. The problem was that during my initial tests I did
r was already closed.
Sorry for that.
Regards,
Daniel Migowski
-Ursprüngliche Nachricht-
Von: Johan Corveleyn [mailto:jcor...@gmail.com]
Gesendet: Donnerstag, 17. Juli 2014 11:58
An: Daniel Migowski
Cc: Andreas Stieger; users@subversion.apache.org
Betreff: Re: subversion destroys my Wo
On Thu, Jul 17, 2014 at 11:23 AM, Daniel Migowski wrote:
> Hello Andreas,
>
>
>
> my editor (current Eclipse 4.4) locks my build.xml files, even after I
> closed them in the Editor. This is a bug, alright, but nonetheless I feel
> that subversion should never leave the Working Copy in a state wher
agree? This behaviors seems much better.
Regards,
Daniel Migowski
Von: Andreas Stieger [mailto:andreas.stie...@gmx.de]
Gesendet: Donnerstag, 17. Juli 2014 07:44
An: Daniel Migowski
Cc: users@subversion.apache.org
Betreff: Re: subversion destroys my Working Copy
Hi,
On 17 Jul 2014, at 02:41, Daniel
Hi,
> On 17 Jul 2014, at 02:41, Daniel Migowski wrote:
>
> This always occurs when I commit a resource already open in an editor which
> contains a @revision tag. The commit message looks like this:
>
> C:\IKOfficeRoot\Java\ERP\Core\build.xml
> C:\IKOfficeRoot\Java\ERP\Framework\data\template
Hello,
within 2 days TortoiseSVN destroyed my Working Copy six times. This always
occurs when I commit a resource already open in an editor which contains a
@revision tag. The commit message looks like this:
C:\IKOfficeRoot\Java\ERP\Core\build.xml
C:\IKOfficeRoot\Java\ERP\Framework\data\templat
