[Top][All Lists]

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

Re: [Gnu-arch-users] moving an archive

From: Bruce Stephens
Subject: Re: [Gnu-arch-users] moving an archive
Date: Mon, 15 Sep 2003 17:18:04 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux)

Zack Brown <address@hidden> writes:

> On Tue, Sep 16, 2003 at 01:00:49AM +1000, Robert Collins wrote:
>> On Tue, 2003-09-16 at 00:48, Zack Brown wrote:
>> > On 25 Aug 91 20:57:08 GMT, Linus Torvalds wrote:
>> > > It is NOT protable (uses 386 task switching etc), and it probably never
>> > > will support anything other than AT-harddisks, as that's all I have :-(.
>> > 
>> > What exactly ties a category to a particular archive? Isn't it just
>> > string data within the category itself? And if so, won't a simple
>> > search-and-replace operation modify all those strings appropriately?
>> And what if someone has already branched off the archive? you'll update
>> them as well? And their offshoots? And the signed patches one of the
>> forks from them?
> That's a good point. But why is the name of the archive included in
> the category itself? It doesn't seem releavant, and if it weren't
> there then a straight 'mv' might have a hope of working.

There's nothing special about a category name.  patchlogs contain
names of revisions, and to specify a revision you need the archive
name, category, branch, version and patchlevel.

patchlogs get stored in along with the source in changesets.  So if
you want to move things in this way you'll need to do horrible stuff.
Best not to, altogether.  Sometimes it might seem convenient to do
this---you might want to split an archive, for example, moving some
categories in a different archive.  But that's just not going to work
easily---it's likely to be better to tag into a new archive, and
accept that the older revisions are going to stay where they are,
forever.  You can minimise access by caching -base-0 of the new
category, but there'll be some things (ancestry, ancestry-graph for
example) that may well try to access the old archive anyway.


reply via email to

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