summaryrefslogtreecommitdiff
path: root/HACKING
AgeCommit message (Collapse)Author
2010-01-06maint: apply correct license to auxiliary filesEric Blake
* gnulib: Update, for maint.mk improvements. * HACKING: Use GFDL 1.3, not 1.2. * NEWS: Likewise. * README: Likewise. * cfg.mk (old_NEWS_hash): Update accordingly. * .gitignore: Ignore file created by 'make update-NEWS-hash'.
2010-01-01maint: update all FSF copyright year lists to include 2010Jim Meyering
Use this command: git ls-files | grep -v COPYING \ | xargs env UPDATE_COPYRIGHT_USE_INTERVALS=1 \ build-aux/update-copyright
2009-08-25doc: HACKING: mention the new space-only indentation policyJim Meyering
2009-08-25global: convert indentation-TABs to spacesJim Meyering
Transformed via this shell code: t=$'\t' git ls-files \ | grep -vE '(^|/)((GNU)?[Mm]akefile|ChangeLog)|\.(am|mk)$' \ | grep -vE 'tests/pr/|help2man' \ | xargs grep -lE "^ *$t" \ | xargs perl -MText::Tabs -ni -le \ '$m=/^( *\t[ \t]*)(.*)/; print $m ? expand($1) . $2 : $_'
2009-07-14doc: point to Guile's ChangeLog-writing guidelinesJim Meyering
* 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.
2009-06-03doc: HACKING: minor adjustments, additionsJim Meyering
* 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.
2009-06-02doc: HACKING: mention the GNU Coding StandardsJim Meyering
* HACKING (Add documentation): Add a link to the GCS.
2009-05-17maint: HACKING: mention a few more useful git commandsJim Meyering
* HACKING (Miscellaneous useful git commands): Add a few.
2009-03-04policy: use git to help avoid trailing white spaceRalf Wildenhues
* HACKING (Avoid trailing white space): Describe how git can help.
2009-02-27* HACKING: avoid trailing white spaceJim Meyering
2009-02-18doc: explain how to recover from changes committed to masterJim Meyering
* HACKING: A beginner's commit-to-master is so common, and causes enough confusion, that we describe how to recover.
2009-02-18maint: add copyright noticesJim Meyering
* HACKING: Add copyright notice. * tests/test-lib.sh: 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.
2008-11-17doc: HACKING: reference http://www.gnu.org/licenses/why-assign.htmlJim Meyering
Suggestion from Patrick Schoenfeld.
2008-07-16* HACKING: describe how to find a misplaced change-setJim Meyering
2008-06-26* HACKING: use shorter "-1" (over HEAD~1) with git format-patchJim Meyering
2008-06-17HACKING: Add section for tips on reducing translator workload.Bo Borgerson
* HACKING (Be nice to translators): New section. Add Jim's suggestion to avoid changing translatable strings if possible.
2008-06-15update HACKING guidelinesJim Meyering
* HACKING: Don't suggest --signoff; it's redundant. (log requirements): Specify preferred forms. Mention preference for "<" over ">". Mention the "const placement" preference.
2008-05-16make HACKING slightly more genericJim Meyering
* HACKING: remove some uses of "coreutils" Point to git's own SubmittingPatches URL.
2008-04-30Add Daniel Dunbar's lcov instructions to HACKINGBo Borgerson
* 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>
2008-04-27tweak HACKING adviceJim Meyering
2008-04-02HACKING: rename README-contribution-guidelinesJim Meyering
README-contribution-guidelines: Rename to .. HACKING: ...this.