Message-ID: <1106217035.41ef884b6ae51@webmail.imag.fr>
Date: Thu, 20 Jan 2005 11:30:35 +0100
From: Matthieu MOY <Matthieu.Moy@imag.fr>
To: Colin Fox <cfox@cfconsulting.ca>
References: <41EEECAD.5070705@cfconsulting.ca>
	<20050120001634.GJ16408@hezmatt.org>
	<41EF1351.9050000@cfconsulting.ca>
In-Reply-To: <41EF1351.9050000@cfconsulting.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
User-Agent: Internet Messaging Program (IMP) 3.1
Cc: Matthew Palmer <mpalmer@hezmatt.org>, gnu-arch-users@gnu.org
Subject: [Gnu-arch-users] Re: Re: Archive configuration recommendations
Precedence: list
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Content-Transfer-Encoding: 8bit
Status: RO
Content-Length: 1212
Lines: 37
Quoting Colin Fox <cfox@cfconsulting.ca>:

> What would the pros and cons be for mirroring vs tagging a single
> project?

Mirroring makes a read-only copy. Tagging creates a continuation on which you
can commit. They are two different operations with different purpose.

> If my subcontractors mirror, does that mean they mirror the
> whole archive, even if they're only working on one project within the
> archive? If that's the case, it seems like overkill.

You can limit the mirroring to a version.

> Ok, that makes sense. The only thing is -- I don't want to have to
> register an archive for each developer so I can get their changes back.

Registering an archive is one command line, and is done once for each archive.
Much simpler than sending a mail for each merge. Furthermore, some commands like
"tla missing" or "tla star-merge" won't be available if you don't have acces to
the archive.

-- 
Matthieu

-------------------------------------------------
envoyé via Webmail/IMAG !


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