gnu-arch-users
[Top][All Lists]
Advanced

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

Re: [Gnu-arch-users] Inconsistency of Added-files and Removed-files


From: Aaron Bentley
Subject: Re: [Gnu-arch-users] Inconsistency of Added-files and Removed-files
Date: Tue, 17 Aug 2004 14:57:03 -0400
User-agent: Mozilla Thunderbird 0.5 (X11/20040309)

Tom Lord wrote:
    > From: Mikhael Goikhman <address@hidden>

    > Moreover, I would like to request several more log headers, like the ones
    > to report permission or symlink changes, and the one to report changeset
    > type (normal, tag, import, base).

I agree that we want to have all that information available for quick
access but I'm not so sure I agree that it belongs in patch logs.

A lot of core developers are (rumours have it) brainstorming about
what to include a future currently-theoretical change to the format of archives.

Did you know about the Format 3 wishlist?

http://wiki.gnuarch.org/moin.cgi/Archive_20Format_203_20Wishlist

I wonder if all this changeset-implied meta-data (permission changes,
a readily computable tree inventory, etc. should be added to the
archive format as new files.  So.... there's the patch-log in each
revision, sure, but there's also some files that help compute the tree
inventory and everything that implies pretty quickly without having to
build the tree itself.

Which I guess implies that it's easily available in the archive like patchlogs are?

This might also be a better place to store version variables. I'd like to at least have the option of storing *lots* of version variables.

And while we're at it, I'd like inventory-ID-based versions of new-files, modified-files, etc. I don't like kinda-sorta knowing which revisions modified a given file :-)

Aaron

--
Aaron Bentley
Director of Technology
Panometrics, Inc.




reply via email to

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