Date: Fri, 26 Nov 2004 16:12:16 +0100
From: Andre Kuehne <andre.kuehne@gmx.net>
To: gnu-arch-users@gnu.org
Message-ID: <20041126151216.GA8542@aku>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: [Gnu-arch-users] Improving Archive Cached Revisions
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: 927
Lines: 34
Hey guys,

The current Archive Cached Revisions implementation seems a little brute force
to me. A logical step to a more flexible solution would be something like this:

"tla cacherev --level 0"
    standard cached rev (full backup)
"tla cacherev --level 1"
    cached rev is a changeset from the last level 0 cached rev
"tla cacherev --level 2"
    ...

This would be especially helpful for large projects with lots of small
changesets, but also in general. Tom's maxime that disk space is cheap
(http://regexps.srparish.net/www/arch-tech.html#cheapdisk) doesn't mean
you have to throw it away ;)

(If this was discussed already, some hint would be nice.)

Regards

-- 
     _   _
_/\_| |_( )_
Andre Kuehne


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