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

Re: printing full path on commit

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-03-31 19:41:56 CEST

Patrik Husfloen <pathu440@student.liu.se> writes:
> I also noticed when doing a status check after committing I get:
> ? ./test.jpg
>
> shouldn't the file be marked with "D" instead of "?" (and also, let me
> point out the inconsistency with the checkin as here it only prints ./
> and the checkin printed the whole path, from c:\ and up)

No. You didn't remove the file itself, but it's no longer under
revision control. Therefore, it's just another random file cluttering
up the working copy. :-)

I had thought our behavior was to remove it if it has no local mods,
but leave it if it does. Is svn just always leaving it?

> also, doing svn update ouptuts
> D ./test.jpg
>
> but doesn't delete the file (I find that "wrong" but it might be as it
> should)
> so, the file is still there, and doing svn status shows:
> ? ./test.jpg

Yeah, the update behavior is a known bug, see

   http://subversion.tigris.org/issues/show_bug.cgi?id=658

> it seems to me that updating would delete the file, I might add that
> I'm pretty new to version control in general so this might indeed be
> the intented behaviour.

Update shouldn't be doing anything with the file in *that* working
copy, because that's the working copy the deletion was committed from.
In other working copies, same local mod rule: delete the working file
on update unless it has local mods.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 31 19:35:34 2002

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