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

Re: Confusing update + commit semantics

From: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2005-09-21 16:32:05 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?

Yes. No changes were made to the older file, so there was nothing to commit.
What you're looking for is:

> 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?



Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner
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:35:30 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.