From: Bert Huijben [mailto:b...@qqmail.nl], Sent: Friday, October 25, 2013 9:46
AM
> Can you post an 'svn status' output of your working copy?
Not a full one; I do have an unresolved file conflict (along with a few
other normal edits), which would have been the case when I did the update:
D C drx\Source\Workspaces\Project\gnu-projectname.mak
> moved to drx\Source\Workspaces\Project\gnu-project.mak
> local file moved away, incoming file edit upon update
> Without this (or a reproduction script that shows us in what state
> your working is in) your bug report contains not enough
> information to diagnose.
Figured as much, but I thought I'd mention it (as the popup asked me to).
I'll keep an eye on it (e.g., in case that file gets changed remotely again).
It's probably worth mentioning that this particular manoeuvre (the file
rename) was done with SVN 1.7.x, and the WC was upgraded to 1.8 with that
unchecked-in, in case the new 1.8 rename methodology is at play/fault here.
--
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit
