Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/ https://git.shady.money/coreutils/atom?h=v8.26 2016-11-22T20:04:24Z 2016-11-22T20:04:24Z Pádraig Brady P@draigBrady.com 2016-10-31T13:29:34Z urn:sha1:ea94589e9ef02624a3837f97f80efd7d3dcf56bf Note we don't support the --algorithm option of the b2sum command in the external BLAKE2 project, as that was deemed too confusing for users. "BLAKE2b" was chosen as the default algorithm to use, which is single threaded but performs well on 64 bit. * src/blake2: CC0 source copied from external project. * cfg.mk[VC_LIST_ALWAYS_EXCLUDE_REGEX]: Exclude blake2/ from syntax checks, make update-copyright, etc. * src/local.mk: Reference the sources for b2sum, and set the compilation flags. * doc/coreutils.texi (b2sum invocation): Reference the md5sum invocation node, and add descriptions of -l. * tests/misc/b2sum.sh: Add new test. * tests/local.mk: Reference new test. * AUTHORS: Add new binary. * README: Likewise. * build-aux/gen-lists-of-programs.sh: Likewise. * man/.gitignore: Likewise. * scripts/git-hooks/commit-msg: Likewise. * man/b2sum.x: New man page template. * man/local.mk: Reference new template. * src/.gitignore: Ignore new binaries. * src/blake2/.gitignore: Ignore new build atrifacts. * src/md5sum.c (usage): Describe the new -l option. * NEWS: Mention the new program. 2015-11-23T11:16:17Z Pádraig Brady P@draigBrady.com 2015-11-23T11:10:31Z urn:sha1:561f759b01cedda112d696071d205d26b9196d89 To support "md5sum,sha*sum:" Suggested by Bernhard Voelker. 2015-11-17T10:42:37Z Jim Meyering meyering@fb.com 2015-08-20T15:50:31Z urn:sha1:dab71a37d0fed9bd93db3d8b3779ca86c0c453ec 2015-10-29T00:18:13Z Pádraig Brady P@draigBrady.com 2015-10-28T10:56:56Z urn:sha1:3f5e0453e17bd9db231d2fc7ba112821c428d0fc To tag changes that are user visible and affect all (or many) commands. 2015-09-02T23:33:19Z Pádraig Brady P@draigBrady.com 2015-08-05T08:28:36Z urn:sha1:89c517d9e26ad232d857ba37d897adbef19b30a9 Suggested in https://bugzilla.redhat.com/1250113 * AUTHORS: Add base32. * THANKS.in: Add suggester. * README: Reference the new program. * NEWS: Mention the new program. * src/.gitignore: Ignore the new binary. * bootstrap.conf: Reference the gnulib base32 module. * build-aux/gen-lists-of-programs.sh: Add base32. * man/base32.x: A new template. * man/.gitignore: Ignore the new man page. * man/local.mk: Reference the new man page. * doc/coreutils.texi (base32 invocation): Document the new command. * src/local.mk: Adjust to build base32 based on base64.c. * src/base64.c: Parameterize to use the correct headers, functions and buffer sizes, depending on which binary is being built. * tests/misc/base64.pl: Adjust to test both base32 and base64. * tests/misc/tty-eof.pl: Add base32 as a program that accepts input on stdin without any options specified. * scripts/git-hooks/commit-msg: Add base32 to the template. 2015-01-25T15:47:13Z Jim Meyering meyering@fb.com 2015-01-06T15:51:01Z urn:sha1:44074d8f77caa085f75e27b73e06c8301992cf84 * scripts/autotools-install: Increase automake's version number to 1.15 and add Stefano Lattarini's new GPG key ID. Increase gettext's version to 0.19.4 and add Daiki Ueno's GPG key ID. Also move VERSION definition "up" so that it is once again automatically updated via the emacs hook snippet at the end of the file. 2014-05-04T21:50:58Z Jim Meyering meyering@fb.com 2014-03-29T16:23:05Z urn:sha1:7182e4470a1c60c410d5b460818ebff0992fd34c * scripts/autotools-install (tarballs): Update to latest. 2014-03-13T17:15:28Z Jim Meyering jim@meyering.net 2013-08-05T14:28:34Z urn:sha1:42d2377b813507d50f5a67076bb20134ceb2fc10 * scripts/autotools-install: Update version numbers of latest automake and gettext packages. 2013-04-22T17:26:25Z Jim Meyering meyering@fb.com 2012-12-05T19:11:59Z urn:sha1:090294b0e4b496137fcb3a672c979c679d0e47f8 * scripts/autotools-install (tarballs): Use http:// URLs rather than ftp:// ones. The former are more likely to work, these days. Update URLs to point to the latest versions. 2013-02-18T01:28:49Z Stefano Lattarini stefano.lattarini@gmail.com 2013-02-15T13:39:40Z urn:sha1:5bff307bdbee76adad7a7990cc23d8fd43b76252 Git honours the GIT_EDITOR environment variable, the "core.editor" Git configuration variable, and the EDITOR environment variable (in that order, and defaulting to "vi" if none of them is set) to decide which editor should be invoked for the user when he has to or want to edit his commit message. However, our commit-msg hook, when invoking an editor on behalf of the user to allow him to fix a non-policy-complaint commit message, only honoured the EDITOR environment variable. To avoid potential annoying inconsistencies, we should really use the same logic used by Git in the selection of the editor. Luckily, we don't have to duplicate this logic (that would be brittle in the long term), as we can rely on the "git var" command, designed exactly to be used in situations like this. * scripts/git-hooks ($editor): Adjust definition.