Awesome, thanks Matt. Sorry I havn't managed to make the changes you requested on ReviewBoard. If you don't get to it before Thursday, I'll give it a go :)
On 31 December 2013 13:29, Matthew Jordan <mjor...@digium.com> wrote: > On Sun, Dec 22, 2013 at 3:17 PM, George Joseph > <george.jos...@fairview5.com> wrote: > > > > > > > > On Sun, Dec 22, 2013 at 1:25 PM, Ben Langfeld <b...@langfeld.me> wrote: > >> > >> But how do I know which one of those is which hash, since they're not > labelled? > > > > > > The *sum programs can tell by the length. md5 is 32, sha1 is 40, sha256 > is 64, etc. They ignore with warnings lines that don't match length. > > > > Since this has been up on Review Board for awhile and no one else has > commented on it, I'm going to go ahead and commit it today. > > The resulting scheme will be: > * Separate files for md5, sha1, and sha256 > * Checksum results for both tarballs and patch files in a single file > > Matt > > -- > Matthew Jordan > Digium, Inc. | Engineering Manager > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at: http://digium.com & http://asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
