Date: Sun, 14 Nov 2004 12:49:49 -0600
From: "Karl O. Pinc" <kop@meme.com>
To: Charles Duffy <cduffy@spamcop.net>
Subject: Re: [Gnu-arch-users] Removing the last changeset(s) from the archive
Message-ID: <20041114124949.M15533@mofo.meme.com>
References: <20041114111431.E15533@mofo.meme.com>
	<1100454735.15201.24.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
In-Reply-To: <1100454735.15201.24.camel@localhost>;
	from cduffy@spamcop.net on Sun, Nov 14, 2004 at 11:52:15 -0600
Cc: gnu-arch-users@gnu.org
Precedence: list
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 1261
Lines: 24

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 <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/