> --- Ursprüngliche Nachricht ---
> Von: email@example.com
> An: Jason Dunham <firstname.lastname@example.org>
> Kopie: email@example.com, firstname.lastname@example.org,
> Betreff: Re: Forcing a commit
> Datum: 23 Jun 2005 13:34:34 -0500
> Jason Dunham <email@example.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
> firstname.lastname@example.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.
You could use svnput: it's a utility that 'puts' a file into the repository,
overwriting what's already there. You don't even need a working copy.
It's in the subversion repository in the tools/ or contrib/ dir.
Geschenkt: 3 Monate GMX ProMail gratis + 3 Ausgaben stern gratis
++ Jetzt anmelden & testen ++ http://www.gmx.net/de/go/promail ++
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jun 23 21:44:47 2005