Date: Tue, 12 Oct 2004 11:57:58 -0700
From: Sriram Ramkrishna <sri@aracnet.com>
To: James Blackwell <jblack@merconline.com>
Subject: Re: [Gnu-arch-users] sharing local archive problems
Message-ID: <20041012185758.GC28463@aracnet.com>
References: <20041012085047.GB15654@avorop.local>
	<20041012141819.BDD55127336@comet.merconline.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041012141819.BDD55127336@comet.merconline.com>
User-Agent: Mutt/1.4.1i
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: 1037
Lines: 28
On Tue, Oct 12, 2004 at 10:18:19AM -0400, James Blackwell wrote:
> If you insist upon having a shared archive, then you have three choices: 
> 
> 1. Use a shared account, typically by creating a new account, and adding
> both his and your ssh keys to authorized_keys for that account.
> 
> 2. Keep seperate accounts. Though some people manage to pull this off by
> fiddling with permissions and umasks, it seems that most people end up
> in permissions hell. 
> 
> 3. Set up a patch queue manager like arch-pqm. Though this will general
> solve more problems than it creates, this solution isn't flawless
> because of an edge case in star-merge that is magnified by the behavior
> a pqm encourages.

Or decide which of your branches is main branch and you could merge
everyone's changes and be the human arch-pqm.

sri


_______________________________________________
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/