On Tue, Oct 24, 2006 at 06:34:21PM -0700, Bill Shannon wrote: > Right, but they might still be only part of a larger change that I'm in > the middle of. > > If I've got files checked out, I don't think it's a safe assumption that > you should push the most recently checked in versions of those files, nor > necessarily the checked in versions of other files.
Yes, this is why in our Xen gate we have a 'putback' script that complains if there's local changes. > >Is that true? If I have a Teamware workspace and go fire off a build in > >the workspace - and then you tried to do a putback to my Teamware > >workspace - would Teamware block it? > > A build won't block a putback, and for that reason you probably don't > want to be building in the parent workspace. You should build in a > child workspace where you control what changes when. > > But with Teamware I can and often do *read* the files in the parent > workspace. It's easy to add a hook to make the parent update. In the parent's .hg/hgrc, add something like: [hooks] incoming = hg update so the parent updates every time someone pushes. Again, this is something that we'd likely customise ourselves... regards john _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
