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

Re: commit allowed without update first?

From: <kfogel_at_collab.net>
Date: 2004-06-11 16:21:57 CEST

"Jacques Carette" <carette@mcmaster.ca> writes:
> PS: is there a feature whereby one can completely disallow unmerged
> commits? It should not be the default, but in certain settings it
> would be appropriate.

If I understand what you're asking for correctly, it is not possible.
There is no way to automatically determine whether two commits have
been "merged" or not, because the definition of "merged" is up to

Subversion does the best it can: if the changes conflict, it puts the
working file into a 'conflicted' state, and the user must run the
command 'svn resolved' to get it out of that state before committing.

Whether you actually make any changes to the file (such as removing
the conflict markers) is a matter of human judgement. There are some
contexts where the appropriate "merge" action is to edit nothing and
commit. The 'svn resolved' command exists solely for humans to have a
way to tell Subversion that the file is ready for commit.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 11 17:44:54 2004

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.