Tom Lord wrote:
From: John Arbash Meinel <[EMAIL PROTECTED]>
Why doesn't arch assign the id based on the patch log fully qualified
revision?
It *does*. It does that too. The same id makes sense when viewed that
way or when viewed as simple algebra on relative path names.
That's the point. Why fuss with it?
-t
The id is currently:
A_./{arch}/c/c--b/c--b--v/a/patch-log/r
I'm wondering why it isn't just
A_a/c--b--v--r
The issue is that as long as you keep the directory structure the same,
there is no difference. But if you want to move where files are stored
(as in what I'm trying to do), you have to leave the arch-id as the
original path-based name.
I'm doing that, but it doesn't *feel* like the correct thing. The id
shouldn't be caught up in a specific implementation of the arch protocol.
John
=:->
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Gnu-arch-users mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-arch-users
GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
