> -----Original Message-----
> From: Mark Parker [mailto:mark@msdhub.com]
> Sent: Tuesday, November 22, 2005 4:24 PM
> To: Subversion Users
> Subject: Interesting situation in my WC, can't commit a changed file
>
> As way of background, I'm currently working on a project which is
going
> to be making a change of platform. I've got my WC that I always had,
> running on the old platform, and a new WC with only the changes
> (uncommitted) needed to make it run on the new platform.
>
> Now, I've run into a situation. One of the files that had changed in
the
> new WC was moved in the old WC and committed. I updated in the new WC,
> and the old file was made unversioned (expected) and the file from the
> old WC appeared in the new location (also expected). However, when I
> manually moved the modified file into it's new location in the new WC,
> subversion doesn't believe that it's modified.
After several minutes I concluded that WC must refer to web component
and not water closet. See http://www.holysmoke.org/wb/wb0044.htm for
background on why this was confusing. :)
> My question is, how do I make subversion recognize that it needs to be
> committed?
Change something else. I know it is a hack, but insert a space or
newline somewhere and it will probably recognize the change. I've had
this happen to me once or twice, but I haven't ever been able to
reproduce it.
--Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 22 22:49:48 2005