[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 20:34:34 CEST

Jason Dunham <jdunham@sfis.com> writes:
> There are two of us developing on the same source code in the trunk.
> If my coworker commited the last installer image, and then I make a
> new build, then I have to update to get his stale installer build
> before I can commit the current one.

Thanks, now I understand.

> I like the property idea. 99% of our files work great with
> Subversion's exsisting functionality, including everything in the
> trunk (the source).
> But we have a whole "build" branch with about a dozen installer
> images, and I'd like to run a commit on the whole folder and have
> newer files overwrite whatever is currently in the repo. So I would
> set a property on the whole build folder so that I could force the
> commit on any newer file. Of course if my coworker changed one of the
> other images, my older copy should remain uncommitted. If that's hard
> to enforce, it would be fine to just run the commit on the specific
> subfolder with a --ignore-conflicts flag.

Gosh. I'm just not sure whether the other devs would go for this, and
I'm not sure how I feel myself.

Would you like to post an enhancement proposal to
dev@subversion.tigris.org and see what kind of reaction you get? Use
all the mails that have happened in this thread already, according to
your judgement, and discard anything that seemed like a dead end.

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