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

Re: Forcing a commit

From: <kfogel_at_collab.net>
Date: 2005-06-23 01:39:41 CEST

Jason Dunham <jdunham@sfis.com> writes:
> I've searched the archives on this, and it seems apparrent that
> Subversion has no analog for the CVS -f option to force a commit.
> Our development team would like to force commits for built binaries.
> We store the binaries in the subversion repository because it's a
> great way to archive our builds and distribute them to coworkers and
> testers. Maybe that's outside the scope of Subversion, but it works
> really well for our team. However, it's irritating to have to update
> the folders which store the installer images. These folders are not
> sotred in the trunk, but in a separate tree for builds, parallel to
> the trunk.

Why are you having to update the folders?

> The developers never care if there is a conflict, and on a slow net
> connection it is frustrating to have to perform a big worthless update
> right before a big commit.
> Even better than a -f option on commit would be a svn:ignoreconflict
> property.

I think we'd want a --ignore-conflicts option, and/or an
"svn:resolution" property that says how to resolve a conflict (values
could be 'working', 'new', 'old', etc). Thoughts?

If I understood why you have to do that update, that'd help a lot,


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 23 02:26:11 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.