[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnu-arch-users] multi-committer functionality revisited

From: Robert Anderson
Subject: [Gnu-arch-users] multi-committer functionality revisited
Date: Mon, 17 Nov 2003 16:36:39 -0500

I'm running into essentially the same problem that the "Xouvert
guy" brought up some time ago.  Only my situation is a little
different in that sftp is not involved.

I am working in an NFS environment where all access to an archive
is "local."  After confused looks of "isn't this a little
complicated for what we're trying to do" when trying to suggest
that we each keep our own archives and have one person do merging
work into a "mainline", I acquiesced and said that for some
branches, we can all just commit directly (because there's really
no reason to do otherwise from a process standpoint in this
context).  Well, I seem to have lied, as this is not working
smoothly at all.

The problem is of course that due to a non-negotiable,
shop-mandated umask, the ++revision-lock directory is not group
writable, and each person who commits locks out all the others
until they make it so.  This is problematic both functionally and
in the "why are you giving us this crap tool which chokes on the
most basic of operations" depts.

So I'm looking for a solution.  In the "not acceptable" category
are additional "committer accounts" (you'll just have to accept
that this is not possible - I don't have root access and the
people who do would never create such an account).

Any other ideas?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]