Received: from spf5.us4.outblaze.com (spf5.us4.outblaze.com [205.158.62.27]) by sdf.lonestar.org (8.13.1/8.12.10) with ESMTP id j15GXCao009421 for ; Sat, 5 Feb 2005 16:33:13 GMT Received: from hera.museatech.net (unknown [207.166.200.220]) by spf5.us4.outblaze.com (Postfix) with SMTP id 04DFE77105 for ; Sat, 5 Feb 2005 16:34:02 +0000 (GMT) Received: (qmail 19619 invoked by uid 110); 5 Feb 2005 16:33:54 -0000 Received: from gnu-arch-dev-bounces@lists.seyza.com by hera by uid 102 with qmail-scanner-1.20 (clamscan: 0.60. spamassassin: 2.60. Clear:RC:1(127.0.0.1):. Processed in 2.179151 secs); 05 Feb 2005 16:33:54 -0000 Received: from unknown (HELO hera.museatech.net) (127.0.0.1) by hera.museatech.net with SMTP; 5 Feb 2005 16:33:52 -0000 Delivered-To: list-gnu-arch-dev@lists.seyza.com Received: (qmail 19537 invoked by uid 110); 5 Feb 2005 16:33:41 -0000 Received: from john@arbash-meinel.com by hera by uid 102 with qmail-scanner-1.20 (clamscan: 0.60. spamassassin: 2.60. Clear:RC:1(207.166.200.201):. Processed in 2.553884 secs); 05 Feb 2005 16:33:41 -0000 Received: from unknown (HELO a1.mx.alal.us) (207.166.200.201) by hera.museatech.net with SMTP; 5 Feb 2005 16:33:38 -0000 Received: (qmail 30828 invoked from network); 5 Feb 2005 17:46:50 -0000 Received: from ct.radiology.uiowa.edu (129.255.60.186) by a1.mx.alal.us with SMTP; 5 Feb 2005 17:46:47 -0000 Received: from [192.168.1.11] (12-217-241-0.client.mchsi.com [12.217.241.0]) by ct.radiology.uiowa.edu (8.11.6/8.11.6) with ESMTP id j15GXW326601; Sat, 5 Feb 2005 10:33:32 -0600 Message-ID: <4204F55A.5030901@arbash-meinel.com> Date: Sat, 05 Feb 2005 10:33:30 -0600 From: John A Meinel User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Anand Kumria Subject: Re: [GNU-arch-dev] Re: tla-1.4pre1 now available References: <87d5vinquw.fsf@flame.org> In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on dev.alal.com X-Spam-Level: X-Spam-Status: No, score=-1.6 required=9.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.2 Cc: gnu-arch-users@gnu.org, gnu-arch-dev@lists.seyza.com X-BeenThere: gnu-arch-dev@lists.seyza.com X-Mailman-Version: 2.1.5 Precedence: list List-Id: a mailing list for GNU Arch developers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1558873051==" Mime-version: 1.0 Sender: gnu-arch-dev-bounces@lists.seyza.com Errors-To: gnu-arch-dev-bounces@lists.seyza.com Status: RO Content-Length: 3153 Lines: 94 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1558873051== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig15D440732132DDB7492126DD" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig15D440732132DDB7492126DD Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Anand Kumria wrote: ... >There was some discussion on the devel mailing list about whether this >should be a phased introduction (i.e read new archives in 1.4, write old >by default; write new archives in 1.5). > >But considering that anyone upgrading will also have to do an >archive-fixup, I think you should just make this change directly. > > > I thought this was a compatible archive-fixup. It just adds some files to the root level .listing file, which previous versions had accidentally left out. >There was a similar change in 1.3 (inode signatures) which meant I had to >upgrade all my developers to 1.3 as soon as it was released and there was >a single user of tla-1.3 > > > Aren't inode signatures only in the local working directories. I know there was something about them being accidentally committed to the archive, but they should be ignored, as they only have meaning on your personal machine. (The inode on my machine does not correspond to the inode on your machine). Now if you were using a shared revlib or something like that, then I could see that a working directory change would cause you to upgrade all of your developers. But I don't believe tla has yet introduced a forward incompatible archive level change in the 1.x series. I know it allowed spaces in filenames in 1.2.1 or so, which means that *if* you used spaces in your filenames, earlier versions couldn't read your archive. But that wasn't really an archive level change (as most were compatible), just an acceptable filename thing. >Also, fixing commit would be good. By that I mean: > - not generate an empty log if $EDITOR is not set > - not generate an empty log if import hasn't been done > - not doing anything if signature generation fails > > > I'm all for these changes. I'm not sure what has been merged in. >Thanks, >Anand > > John =:-> --------------enig15D440732132DDB7492126DD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCBPVaJdeBCYSNAAMRApqoAJ9NgPcme/Ch7NN0pUJfIh6LL8Ay/ACgy4iX HqL+wQhpaBKMKBifepuLw6E= =wPGb -----END PGP SIGNATURE----- --------------enig15D440732132DDB7492126DD-- --===============1558873051== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnu-arch-dev mailing list Gnu-arch-dev@lists.seyza.com http://lists.seyza.com/cgi-bin/mailman/listinfo/gnu-arch-dev --===============1558873051==--