Re: [Gnu-arch-users] Removing the last changeset(s) from the archive

[Karl O. Pinc]

On 2004.11.14 11:52 Charles Duffy wrote:

> A not-so-trivial issue: How do you handle the cases where someone has
> already checked out / branched a version you're deleting?

The easy answer is that you do not allow remote arch access to
arch archives/categories/branches that do allow 'un-commits'.
Perhaps you do not allow anyone who's not 'my-id' to access such
archives/categories/branches, or as this is likely impossible,
set the filesystem permissions so that only the owner has
read access when the archive/category/branch allows 'un-commits'.

You flag the revision when 'allow un-commits' is set and do not
allow uncommits for prior revisions to prevent the case where
somebody has already checked out or branched a version.

If you want both un-commit capability and to share an archive/
category/branch then you have to have a working archive/category/
branch and occasionaly update the corresponding shared copy.

Karl <address@hidden>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein