summaryrefslogtreecommitdiff
path: root/README-hacking
AgeCommit message (Collapse)Author
2009-03-11maint: Document how to best to enable gcc warnings for developersPádraig Brady
* README-hacking: Mention --enable-gcc-warnings configure option * configure.ac: Don't scare developers away from using gcc warnings
2009-02-18add missing copyright datesEric Blake
* 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.
2009-02-13maint: mention how to run a single test in HACKING docsPádraig Brady
* 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.
2009-01-19build: use dist-xz, not dist-lzma, cont'dJim Meyering
* README-hacking: mention XZ utils * README-prereq: Add a FIXME comment.
2008-10-22Add better checks and docs for build toolsPádraig Brady
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.
2008-07-04* README-hacking: Update the section on LZMA.Jim Meyering
2008-01-22* README-hacking: Update to reflect existence of automake-1.10.1.Jim Meyering
2008-01-10* README-hacking: Add Git to the list of required tools.Jim Meyering
2007-10-24Doc improvements.Jim Meyering
* 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.
2007-10-23* README-hacking: Refer to LZMA Utils <http://tukaani.org/lzma/>.Jim Meyering
2007-10-22* README-hacking: Describe how to build with LZMA.Paul Eggert
2007-09-03README-hacking: Require rsync, rather than wget.Jim Meyering
2007-07-23Update all copyright notices to use the newer form.Jim Meyering
2007-07-10Change "version 2" to "version 3" in all copyright notices.Jim Meyering
2007-06-18* README-hacking: Don't mention Gzip 1.2.4, now that 1.3.12 is out.Jim Meyering
2007-06-13* README-hacking: List Gperf as a build-requirement, too.Jim Meyering
Reported by Steve Ward.
2007-05-15Generate a dozen test-related Makefile.am files at bootstrap-time.Jim Meyering
* README-hacking: Build-from-checkout now require Perl, too. * bootstrap: Now that these generated Makefile.am files are no longer under version control, they must be created at bootstrap time.
2007-02-20* README-hacking: Update to reflect that we now use git.Jim Meyering
2007-02-20Now that we use GIT, not cvs, rename README-cvs.Jim Meyering
* README-hacking: Renamed from... * README-cvs: ...this.
generated by cgit v1.2.3-70-g09d2 (git 2.47.0) at 2024-11-16 05:38:59 +0000