coreutils/HACKING, branch v7.5 Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/ https://git.shady.money/coreutils/atom?h=v7.5 2009-07-14T18:43:49Z doc: point to Guile's ChangeLog-writing guidelines 2009-07-14T18:43:49Z Jim Meyering meyering@redhat.com 2009-07-14T18:42:29Z urn:sha1:4612670f467d122e0a4efedcf0ce04951b4f43d8 * HACKING (Commit log requirements): Point to Guile's http://www.gnu.org/software/guile/changelogs/guile-changelogs_3.html. Mention that a bit of prose can be welcome. doc: HACKING: minor adjustments, additions 2009-06-03T16:30:40Z Jim Meyering meyering@redhat.com 2009-06-03T16:28:34Z urn:sha1:d8243c25cdfa90c86b3629f3b723c2d2962e2a22 * HACKING (Amending...): Remove spurious "-e" used with commit --amend. (log message policy): Mention the 72-column limit. "build:" and "maint:" are common prefixes, these days. doc: HACKING: mention the GNU Coding Standards 2009-06-02T14:35:14Z Jim Meyering meyering@redhat.com 2009-06-02T05:52:02Z urn:sha1:18db64ba7e7acc45a56423b2e96ab2c1faffaad2 * HACKING (Add documentation): Add a link to the GCS. maint: HACKING: mention a few more useful git commands 2009-05-17T15:51:13Z Jim Meyering meyering@redhat.com 2009-05-17T15:49:24Z urn:sha1:088a7ca9b155fde8d8af0c3754b7df3d45485591 * HACKING (Miscellaneous useful git commands): Add a few. policy: use git to help avoid trailing white space 2009-03-04T05:19:49Z Ralf Wildenhues Ralf.Wildenhues@gmx.de 2009-03-02T21:33:05Z urn:sha1:0d61f144a318cd54aa903068cbc40276d1b97d22 * HACKING (Avoid trailing white space): Describe how git can help. * HACKING: avoid trailing white space 2009-02-27T22:05:07Z Jim Meyering meyering@redhat.com 2009-02-25T14:37:58Z urn:sha1:d88c9f95e38cb86460ba4acaf90b24c3c8fce8bf doc: explain how to recover from changes committed to master 2009-02-18T14:40:53Z Jim Meyering meyering@redhat.com 2009-02-18T13:50:04Z urn:sha1:0a3f944791cf93b6abbb544ee0b4df6f2b777351 * HACKING: A beginner's commit-to-master is so common, and causes enough confusion, that we describe how to recover. maint: add copyright notices 2009-02-18T14:40:44Z Jim Meyering meyering@redhat.com 2009-02-18T13:34:23Z urn:sha1:fa391362e1e607722b874313dec6cdd9db7c62f4 * HACKING: Add copyright notice. * tests/test-lib.sh: Likewise. maint: mention how to run a single test in HACKING docs 2009-02-13T11:13:33Z Pádraig Brady P@draigBrady.com 2009-02-12T13:51:03Z urn: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. doc: HACKING: reference http://www.gnu.org/licenses/why-assign.html 2008-11-17T10:16:19Z Jim Meyering meyering@redhat.com 2008-11-17T10:16:19Z urn:sha1:8b09875b59e112b01db6e3909003b52447a62a7c Suggestion from Patrick Schoenfeld.