coreutils/HACKING, branch v7.4

policy: use git to help avoid trailing white space

2009-03-04T05:19:49Z

* HACKING (Avoid trailing white space): Describe how git can help.

* HACKING: avoid trailing white space

2009-02-27T22:05:07Z

doc: explain how to recover from changes committed to master

2009-02-18T14:40:53Z

* 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

* 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

* 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

Suggestion from Patrick Schoenfeld.

* HACKING: describe how to find a misplaced change-set

2008-07-16T13:29:04Z

* HACKING: use shorter "-1" (over HEAD~1) with git format-patch

2008-06-26T19:08:22Z

HACKING: Add section for tips on reducing translator workload.

2008-06-17T06:29:23Z

* HACKING (Be nice to translators): New section. Add Jim's suggestion to avoid changing translatable strings if possible.

update HACKING guidelines

2008-06-15T14:01:29Z

* HACKING: Don't suggest --signoff; it's redundant. (log requirements): Specify preferred forms. Mention preference for "<" over ">". Mention the "const placement" preference.