| Age | Commit message (Collapse) | Author |
|---|
|
* HACKING (Avoid trailing white space): Describe how git can help.
|
|
|
|
* HACKING: A beginner's commit-to-master is so common,
and causes enough confusion, that we describe how to recover.
|
|
* HACKING: Add copyright notice.
* tests/test-lib.sh: Likewise.
|
|
* 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.
|
|
Suggestion from Patrick Schoenfeld.
|
|
|
|
|
|
* HACKING (Be nice to translators): New section.
Add Jim's suggestion to avoid changing translatable strings if possible.
|
|
* HACKING: Don't suggest --signoff; it's redundant.
(log requirements): Specify preferred forms.
Mention preference for "<" over ">".
Mention the "const placement" preference.
|
|
* HACKING: remove some uses of "coreutils"
Point to git's own SubmittingPatches URL.
|
|
* HACKING: New section `Finding things to do', points to TODO file and
gives instructions on generating an html coverage report as provided by
Daniel Dunbar.
* TODO: Add item for improving test coverage. Point back to HACKING.
Signed-off-by: Bo Borgerson <gigabo@gmail.com>
|
|
|
|
README-contribution-guidelines: Rename to ..
HACKING: ...this.
|
