summaryrefslogtreecommitdiff
path: root/HACKING
AgeCommit message (Collapse)Author
2015-01-01maint: update all copyright year number rangesPádraig Brady
Run "make update-copyright" and then... * tests/sample-test: Adjust to use the single most recent year. * tests/du/bind-mount-dir-cycle-v2.sh: Fix case in copyright message, so that year is updated automatically in future.
2014-06-26tests: use predetermined NON_ROOT_GIDPádraig Brady
* HACKING: GID is more useful in tests than group name, so rename input param from NON_ROOT_GROUP to NON_ROOT_GID to make it obvious that only a group ID is now acceptable, thus allowing GID lookups to be avoided throughout the tests. * init.cfg (require_root_): Likewise. * tests/misc/truncate-owned-by-other.sh: Avoid looking up the GID. * tests/touch/now-owned-by-other.sh: Likewise. * tests/misc/chroot-credentials.sh: Likewise. Also fix an instance of comparison against NON_ROOT_GROUP which would have given a false failure if a non numeric value was passed in. * tests/id/setgid.sh: Use previously looked up gid as a more accurate base for the subsequent adjustment, and move the uid lookup within chroot, rather than having the overhead of a separate `id` invocation.
2014-01-02maint: update all copyright year number rangesBernhard Voelker
Run "make update-copyright", but then also run this, perl -pi -e 's/2\d\d\d-//' tests/sample-test to make that one script use the single most recent year number.
2013-01-01maint: update all copyright year number rangesJim Meyering
Run "make update-copyright", but then also run this, perl -pi -e 's/2\d\d\d-//' tests/sample-test to make that one script use the single most recent year number.
2012-12-20doc: tweak 'lcov' in HACKINGAssaf Gordon
* HACKING: In the paragraph about creating coverage statistics, use the correct -b (--base-directory) parameter.
2012-12-15doc: mention "git stash" in HACKINGAssaf Gordon
* HACKING: In the paragraph about switching branches, mention "git stash" as a way to continue while preserving uncommitted changes.
2012-12-06maint: adjust HACKING instructions to run a single testAssaf Gordon
* HACKING: Adjust as per the recent changes introduced when switching to non recursive make.
2012-10-13doc: improve HACKING guidelinesNikolas Kallis
* HACKING: Add "cd coreutils" after the git clone command. Copyright-paperwork-exempt: Yes
2012-04-03doc: identify/refer to source of each fixed bug in log and in NEWSJim Meyering
* HACKING (Commit log requirements): Describe our policy: when you fix a bug, put the "git describe" string of the bug-introducing commit in your commit log and put the "fixed-in-release version number" in the NEWS blurb.
2012-01-22maint: quote 'like this' or "like this", not `like this'Paul Eggert
* doc/coreutils.texi (Formatting the file names): coreutils now quotes 'like this'. * man/help2man: * src/timeout.c (usage): Quote 'like this' in diagnostics. * HACKING, Makefile.am, NEWS, README, README-hacking, TODO, cfg.mk: * doc/Makefile.am, doc/coreutils.texi, m4/jm-macros.m4: * man/Makefile.am, man/help2man, src/Makefile.am, src/copy.h: * src/extract-magic, src/ls.c, src/pinky.c, src/pr.c, src/sort.c: * src/split.c, src/timeout.c, src/who.c, tests/dd/skip-seek-past-file: * tests/pr/pr-tests: Quote 'like this' in commentary. * cfg.mk (old_NEWS_hash): Update due to changed old NEWS.
2012-01-01maint: update all copyright year number rangesJim Meyering
Run "make update-copyright".
2011-09-02doc: describe test control variablesPádraig Brady
* HACKING (Add tests): Mention the variables and default values. * README-release (Pre-release testing): Mention that setting the SHELL variable may be required. Suggested by Bruno Haible.
2011-07-27doc: add a vim indentation exampleIvan Sichmann Freitas
HACKING: add a vim example showing how to configure it to follow GNU indentation in coreutils source files.
2011-01-12doc: clean up HACKING guidelinesJim Meyering
* HACKING: Remove mention of "indent-tabs-mode: nil", since we've remove all of those directives. No longer needed. Remove dated (pre-emacs-23) reference regarding WhiteSpace mode.
2011-01-01maint: update all copyright year number rangesJim Meyering
Run "make update-copyright".
2010-12-28coreutils: keep lines within 80-column limitsPaul Eggert
* cfg.mk (LINE_LEN_MAX, FILTER_LONG_LINES): New macros. (sc_long_lines): New rule. * HACKING: Use shorter URLs to the same material. * doc/Makefile.am, doc/coreutils.texi, m4/boottime.m4: * man/help2man, man/stdbuf.x, src/Makefile.am, src/cat.c, src/copy.c: * src/cp.c, src/dd.c, src/df.c, src/du.c, src/groups.c, src/install.c: * src/ls.c, src/md5sum.c, src/mv.c, src/od.c, src/pinky.c, src/ptx.c: * src/readlink.c, src/remove.c, src/rmdir.c, src/setuidgid.c: * src/sort.c, src/tail.c, src/touch.c, tests/Coreutils.pm: * tests/cp/existing-perm-race, tests/cp/perm, tests/cp/preserve-gid: * tests/du/2g, tests/du/long-from-unreadable, tests/init.sh: * tests/install/basic-1, tests/ls/nameless-uid: * tests/ls/readdir-mountpoint-inode, tests/misc/chroot-credentials: * tests/misc/cut, tests/misc/date, tests/misc/join, tests/misc/md5sum: * tests/misc/sha1sum, tests/misc/sha224sum, tests/misc/sort: * tests/misc/sort-continue, tests/misc/sort-files0-from: * tests/misc/sort-rand, tests/misc/stdbuf, tests/misc/tr: * tests/misc/uniq, tests/mv/atomic, tests/mv/part-fail: * tests/mv/part-symlink, tests/mv/sticky-to-xpart, tests/pr/pr-tests: * tests/rm/fail-2eperm, tests/rm/interactive-always: Reformat to fit within 80 columns. * doc/Makefile.am (BAD_POSIX_PERL): New macro. * doc/coreutils.texi: Reword slightly, to make menus and index lines shorter. * src/md5sum.c: Redo --help output so that it fits within 79 columns, since that's a bit more portable and all the other --help strings fit in 79 columns.
2010-04-16* HACKING (Add tests): Change example name, "newtest" to "new-test".Jim Meyering
Not that anyone would confuse with something newt-related, but just because it is more readable that way. doc: tweak HACKING
2010-04-16doc: tweak HACKINGJim Meyering
* HACKING (Curly braces): Tweak a sentence. Filter a few paragraphs through "fmt".
2010-04-15doc: document our code formatting policy regarding curly bracesJim Meyering
* HACKING (Curly braces: use judiciously): New section.
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.
generated by cgit v1.2.3-70-g09d2 (git 2.47.1) at 2024-12-26 19:29:56 +0000