Message-ID: <420132B1.9040000@panoramicfeedback.com>
Date: Wed, 02 Feb 2005 15:06:09 -0500
From: Aaron Bentley <abentley@panoramicfeedback.com>
User-Agent: Mozilla Thunderbird 0.6 (X11/20040530)
MIME-Version: 1.0
To: Kevin Geiss <kevin@desertsol.com>
Subject: Re: [Gnu-arch-users] mirroring concepts/practice help
References: <5a7d482af20133a0b03c35bd22319f92@desertsol.com>
In-Reply-To: <5a7d482af20133a0b03c35bd22319f92@desertsol.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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: 1111
Lines: 33
Kevin Geiss wrote:
> what is the high-level concept/rule involved behind this behavior? I 
> know I would be unable to commit changes in a working tree I get from 
> the mirror, but I thought I could simply check out a working tree to 
> look at it. should I just shut up and make my local archive and start 
> tagging? :)

The concept is: the real name should always be used except when using 
the archive-mirror command.

$FOO is an archive you can get from.  It may or may not be a mirror.
If $FOO is a mirror, $FOO-SOURCE is the upstream archive that you'll use 
to update $FOO.  If you want to create a remote mirror, $FOO-MIRROR is 
the remote mirror, and $FOO is the archive you'll use to update $FOO-MIRROR.

I'm aware that this is messy, and in fact we hope to move to a different 
way of identifying mirrors in baz.

Aaron

-- 
Aaron Bentley
Director of Technology
Panometrics, Inc.


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