Resending to the group in case someone other than Stephan is available to update this ...
Thanks, Karl Date: Sat, 18 Nov 2006 11:31:36 -0800 From: Paul Eggert <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] (Karl Berry) Cc: Stephan Peijnik <[EMAIL PROTECTED]> Subject: gzip import problem with one file m4/shell.m4,v [EMAIL PROTECTED] (Karl Berry) writes: > Stephan Peijnik ([EMAIL PROTECTED]) did the gzip ,v import. And I made you an > admin on the savannah project (and disabled all the "extra" savannah > features). > > Let me know if I can do anything else to help with gzip... Thanks. I have run into a problem with the gzip import. One of the ,v files, originally created by RCS, was corrupted -- it looks like a bad disk block or perhaps an RCS bug. RCS didn't care about the corruption, and local CVS was immune in the few tests I did before sending you the archive, but now I've discovered that remote 'cvs log' does care about the corruption so it's causing me problems. The file in question is gzip/shell.m4, i.e., it's the file that <http://cvs.savannah.gnu.org/viewcvs/gzip/m4/shell.m4?rev=1.4&root=gzip&view=log> refers to. I have attached a gzipped tar file containing the corrected version of m4/shell.mv,v which is 4191 bytes long (a suspicious number, no?) and which has an MD5 checksum of 'b37e1b5ace168570f0740cbfe3d83525'. Can you please fix gzip/m4/shell.m4,v on Savannah? Thanks.
gzip-m4-shell-m4-v.tgz
Description: Binary data
_______________________________________________ Savannah-help-public mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/savannah-hackers
