|
From: | Aaron Bentley |
Subject: | Re: [Gnu-arch-users] caching revisions |
Date: | Tue, 12 Oct 2004 09:28:33 -0400 |
User-agent: | Mozilla Thunderbird 0.5 (X11/20040309) |
Robert Collins wrote:
On Tue, 2004-10-12 at 08:44 -0400, Aaron Bentley wrote:Jason McCarty wrote:The problem is that you tried to cacherev a revision that tla already made a cacherev for. This is a bug, see http://bugs.gnuarch.org/74 . Apparently you can uncacherev it and cacherev it again to fix it.Since I didn't want to tamper with the archive transaction functionality, I changed the cacherev UI so it refuses cacherev when there was already a cacherev. That was merged into 1.2.2rc1 IIRCWith an error? or just returns 0 (as the request, to have a cacherev, has been fulfilled )
With an error. It would be deceptive to claim that a new cacherev had been installed if it hadn't. For example, if you know your cacherev checksums are bogus but don't know you need to uncacherev, you might do cacherev, see no error output, and assume the problem is fixed.
It also saves people's time as they discover very quickly that they no longer need to explicitly cachrev when tagging from a different archive.
Aaron -- Aaron Bentley Director of Technology Panometrics, Inc.
[Prev in Thread] | Current Thread | [Next in Thread] |