coreutils/README-hacking, branch v7.2Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
https://git.shady.money/coreutils/atom?h=v7.22009-03-11T14:52:52Zmaint: Document how to best to enable gcc warnings for developers2009-03-11T14:52:52ZPádraig BradyP@draigBrady.com2009-03-11T12:09:08Zurn:sha1:cf0bb5e05d89d9239a819b696a85532a582c8d38
* README-hacking: Mention --enable-gcc-warnings configure option
* configure.ac: Don't scare developers away from using gcc warnings
add missing copyright dates2009-02-18T13:07:30ZEric Blakeebb9@byu.net2009-02-18T13:07:30Zurn:sha1:86cef85b3671ed0a14a444eef3b6cb07fa26ee64
* NEWS: Add 2009 to copyright.
* README: Likewise.
* README-hacking: Likewise.
* TODO: Likewise.
* doc/Makefile.am: Likewise.
* m4/prereq.m4: Likewise.
* src/nl.c: Likewise.
* src/seq.c: Likewise.
* tests/cp/cp-i: Likewise.
* tests/install/install-C: Likewise.
* tests/install/install-C-root: Likewise.
* tests/install/install-C-selinux: Likewise.
* tests/misc/seq: Likewise.
* tests/mv/mv-n: Likewise.
maint: mention how to run a single test in HACKING docs2009-02-13T11:13:33ZPádraig BradyP@draigBrady.com2009-02-12T13:51:03Zurn:sha1:48cae1e8642684f0103848b84d5884d1ba2412c8
* HACKING: Give an example of how to run a test in isolation.
* README: Fix/simplify example for running a single test.
* README-hacking: Reference the HACKING file.
build: use dist-xz, not dist-lzma, cont'd2009-01-19T12:47:04ZJim Meyeringmeyering@redhat.com2008-11-30T18:35:10Zurn:sha1:9a45c1966716be7f02f8e20f014af720b69aa6fb
* README-hacking: mention XZ utils
* README-prereq: Add a FIXME comment.
Add better checks and docs for build tools2008-10-22T15:31:57ZPádraig BradyP@draigBrady.com2008-10-21T21:40:12Zurn:sha1:99f49949825acc53ae3f0a711ea3e8f96699442d
Prompted by a report from Ed Avis:
<http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/14710>
* README-hacking: Organise LZMA and Valgrind as
as optional requirements rather than in their own sections.
Mention bootstrap will now check tool versions.
* README-prereq: Make a start on specific instructions
for optaining build tools. Currently we just have notes
for Fedora linux.
* bootstrap.conf: Add the list of tools and versions required.
* bootstrap: Add the logic to check for the required tools,
and list all required tools and versions if any are missing.
* README-hacking: Update the section on LZMA.2008-07-04T07:46:31ZJim Meyeringmeyering@redhat.com2008-07-01T14:19:46Zurn:sha1:bba4d3e054cee1f479e6f7239304df676bd63fea* README-hacking: Update to reflect existence of automake-1.10.1.2008-01-21T23:28:23ZJim Meyeringmeyering@redhat.com2008-01-21T23:28:23Zurn:sha1:ec8e146a6db52743451c74d427477a2e9c65e946* README-hacking: Add Git to the list of required tools.2008-01-10T13:43:17ZJim Meyeringmeyering@redhat.com2008-01-10T13:43:17Zurn:sha1:6d80b05c5a6407ef28c994ed8d4c495ffed7188bDoc improvements.2007-10-24T07:13:59ZJim Meyeringmeyering@redhat.com2007-10-24T07:13:59Zurn:sha1:ffc29e91c4ed21ff0b134ec848589b9ae87c1ce6
* README-hacking: Prefer the no-hyphen variant of git commands,
e.g., use "git pull" not "git-pull".
Don't presume that the only way to read this document is via a
prior git clone: provide instructions for cloning coreutils, too.
* README-hacking: Add "cd automake" in build instructions.
From Bob Proulx.
* README-hacking: Refer to LZMA Utils <http://tukaani.org/lzma/>.2007-10-23T13:44:58ZJim Meyeringmeyering@redhat.com2007-10-23T13:44:58Zurn:sha1:def157c9271c3fc601ec8fe7085fb63b25b3e26f