Jim Meyering
ddfcccce51
doc: HACKING: mention the new space-only indentation policy
2009-08-25 09:21:00 +02:00
Jim Meyering
5e778f7c8d
global: convert indentation-TABs to spaces
...
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-08-25 09:21:00 +02:00
Jim Meyering
4612670f46
doc: point to Guile's ChangeLog-writing guidelines
...
* 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-07-14 20:43:49 +02:00
Jim Meyering
d8243c25cd
doc: HACKING: minor adjustments, additions
...
* 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-03 18:30:40 +02:00
Jim Meyering
18db64ba7e
doc: HACKING: mention the GNU Coding Standards
...
* HACKING (Add documentation): Add a link to the GCS.
2009-06-02 16:35:14 +02:00
Jim Meyering
088a7ca9b1
maint: HACKING: mention a few more useful git commands
...
* HACKING (Miscellaneous useful git commands): Add a few.
2009-05-17 17:51:13 +02:00
Ralf Wildenhues
0d61f144a3
policy: use git to help avoid trailing white space
...
* HACKING (Avoid trailing white space): Describe how git can help.
2009-03-04 06:19:49 +01:00
Jim Meyering
d88c9f95e3
* HACKING: avoid trailing white space
2009-02-27 23:05:07 +01:00
Jim Meyering
0a3f944791
doc: explain how to recover from changes committed to master
...
* HACKING: A beginner's commit-to-master is so common,
and causes enough confusion, that we describe how to recover.
2009-02-18 15:40:53 +01:00
Jim Meyering
fa391362e1
maint: add copyright notices
...
* HACKING: Add copyright notice.
* tests/test-lib.sh: Likewise.
2009-02-18 15:40:44 +01:00
Pádraig Brady
48cae1e864
maint: mention how to run a single test in HACKING docs
...
* 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-02-13 11:13:33 +00:00
Jim Meyering
8b09875b59
doc: HACKING: reference http://www.gnu.org/licenses/why-assign.html
...
Suggestion from Patrick Schoenfeld.
2008-11-17 11:16:19 +01:00
Jim Meyering
186b45aaed
* HACKING: describe how to find a misplaced change-set
2008-07-16 15:29:04 +02:00
Jim Meyering
556fbb5721
* HACKING: use shorter "-1" (over HEAD~1) with git format-patch
2008-06-26 21:08:22 +02:00
Bo Borgerson
3435bb7f40
HACKING: Add section for tips on reducing translator workload.
...
* HACKING (Be nice to translators): New section.
Add Jim's suggestion to avoid changing translatable strings if possible.
2008-06-17 08:29:23 +02:00
Jim Meyering
837bb31803
update HACKING guidelines
...
* HACKING: Don't suggest --signoff; it's redundant.
(log requirements): Specify preferred forms.
Mention preference for "<" over ">".
Mention the "const placement" preference.
2008-06-15 16:01:29 +02:00
Jim Meyering
0bf3eb3682
make HACKING slightly more generic
...
* HACKING: remove some uses of "coreutils"
Point to git's own SubmittingPatches URL.
2008-05-16 10:08:56 +02:00
Bo Borgerson
bbc49eb536
Add Daniel Dunbar's lcov instructions to HACKING
...
* 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-30 16:09:33 +02:00
Jim Meyering
cca6a8d7e5
tweak HACKING advice
2008-04-27 21:31:08 +02:00
Jim Meyering
184a0298f3
HACKING: rename README-contribution-guidelines
...
README-contribution-guidelines: Rename to ..
HACKING: ...this.
2008-04-02 09:08:08 +02:00
