Hi Jim, Jim Meyering schrieb: Guenter Knauf wrote: was still something wrong with my last patch? Just the timing ;-) It was a little too close to release time, and applying it, adjusting NEWS and the commit log, reviewing, and testing would have taken time I didn't have. no prob
Hi Jim, was still something wrong with my last patch? Günter.
Hi Jim, Jim Meyering schrieb: Would you like to write the patch (including NEWS and a small doc update), following these guidelines? http://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING I've just tested a bit, and it seems that its enough to hack around the first place where the blank can
Jim, thanks for the very quick review. Jim Meyering schrieb: Guenter Knauf wrote: - size_t i; + size_t i = 0; bool escaped_filename = false; size_t algo_name_len; - i = 0; while (ISWHITE (s[i])) ++i; Instead, please move the declaration down. hmm, not sure what you
was not sure about adding now the openssl format. Find attached the hopefully correct git patch. thanks, Günter. From 941f0d07618d480110dd3417ccb7e1511e8f9504 Mon Sep 17 00:00:00 2001 From: Guenter Knauf li...@gknw.net Date: Sat, 3 Oct 2009 23:24:26 +0200 Subject: [PATCH] added support
Hi Jim, Jim Meyering schrieb: But it's even easier to convert openssl's format into one that is recognized. Filter it through this: sed 's/(/ (/;s/\(= [0-9a-f]*\)$/ \1/' E.g., $ touch f; openssl md5 f MD5(f)= d41d8cd98f00b204e9800998ecf8427e $ openssl md5 f | sed
Hi all, suprisingly I just found that md5sum and sha1sum also accept the formats of the md5 and sha1 tools as input with option -c. There's though a third checksum format which is produced by the openssl tool which only slightly differs to the format from md5 and sha1 - two blanks are missing ...