Subject: Re: [Gnu-arch-users] caching revisions
From: Robert Collins <rbcollins@cygwin.com>
To: Aaron Bentley <abentley@panoramicfeedback.com>
In-Reply-To: <416BDC01.9030000@panoramicfeedback.com>
References: <20041011103527.GA13474@avorop.local>
	<20041011121918.GA5673@iup.edu>	<416BD190.4060606@panoramicfeedback.com>
	<1097586799.5103.50.camel@localhost>
	<416BDC01.9030000@panoramicfeedback.com>
Date: Tue, 12 Oct 2004 23:42:35 +1000
Message-Id: <1097588555.5103.52.camel@localhost>
Mime-Version: 1.0
Cc: Arch Users <gnu-arch-users@gnu.org>, Jason McCarty <bclg@iup.edu>
Precedence: list
Content-Type: multipart/mixed; boundary="===============1815181916=="
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: 2337
Lines: 77

--===============1815181916==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-CBkeBM20lQ0+Ac2xkkqv"


--=-CBkeBM20lQ0+Ac2xkkqv
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-10-12 at 09:28 -0400, Aaron Bentley wrote:
> Robert Collins wrote:
> > On Tue, 2004-10-12 at 08:44 -0400, Aaron Bentley wrote:
> >=20
> >>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=20
> >>functionality, I changed the cacherev UI so it refuses cacherev when=20
> >>there was already a cacherev.  That was merged into 1.2.2rc1 IIRC
> >=20
> >=20
> > With an error? or just returns 0 (as the request, to have a cacherev,
> > has been fulfilled )
>=20
> With an error.  It would be deceptive to claim that a new cacherev had=20
> been installed if it hadn't.  For example, if you know your cacherev=20
> checksums are bogus but don't know you need to uncacherev, you might do=20
> cacherev, see no error output, and assume the problem is fixed.
>=20
> It also saves people's time as they discover very quickly that they no=20
> longer need to explicitly cachrev when tagging from a different archive.

Heh, it also broke some scripts of mine, I hadn't gotten around to
debugging why. How do you feel about an option?

Rob

--=-CBkeBM20lQ0+Ac2xkkqv
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBa99LM4BfeEKYx2ERAlg5AJ9Jw0LHwv+nhHB11kwZ7OG6UADOOACeKusr
g0qQT7qsfuukVwWH7ekOfJU=
=htW9
-----END PGP SIGNATURE-----

--=-CBkeBM20lQ0+Ac2xkkqv--


--===============1815181916==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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