Re: [Gnu-arch-users] Re: Making --setup default in tag and import

[Cameron Patrick]

James Blackwell wrote:

> This is an interesting thought. Check to see the archive is mirrored. If
> not, prune it from the archive, revision library, .arch-cache, etc.

I have a tla-uncommit script (posted to the list) which kind of did
that.  It didn't actually check to see if it was mirrored because in
the general case that's a tricky problem, but it did remove it from
the archive, trim the revision library and re-run archive-fixup.

> But does that cover all cases? What if someone else on the same machine
> points directly at an archive you classify as private but isn't? 

Or over NFS, or whatever.

Darcs has a nifty "unrecord" option that says in the help (roughly),
if you do this when anyone else has got a copy of the patch you're
unrecording, you're screwed.  In practice it's still pretty useful.


Stefan Monnier wrote:

> > But does that cover all cases? What if someone else on the same machine
> > points directly at an archive you classify as private but isn't?
> 
> As already pointed out, the better way to handle it is not to disallow
> mirroring, but to propagate history changes through mirroring, just like any
> other change.  The "Supercedes" header of NNTP is a good starting point.

Wouldn't that still mean that if people tagged off the pre-changed
history, things will break horribly?

Cameron.

signature.asc
Description: Digital signature