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

Confusing update + commit semantics

From: Gerco Ballintijn <Gerco.Ballintijn_at_cwi.nl>
Date: 2005-09-21 16:12:53 CEST


I came across the following confusing subversion behavior. When an svn user
uses the "svn update" command to return a particular file in a directory,
with other modified files, to an older revision (i.e., "down-date" it) and
then uses the "svn commit" command to commit the whole directory, the commit
command silently ignores the file with the older revision, but commits the
other modified files in the directory, leaving the user with the impression
that this older revision is also committed (unless explicitly checking the
"sending" entries). Is this the intended behavior? My collegues expect (or
desire) the "down-dated" file to either be committed anew or have something
like a sticky tag to prevent commit. How can I get to that desired behavior?

With regards,

Dr. G.C. Ballintijn
Interactive Software Development and Renovation
Center for Mathematics and Computer Science (CWI)
Tel. 020-592 4266

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 21 16:15:23 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.