HACKING - OpenGrok cross reference for /coreutils/HACKING

13 For details on building the programs in this package, see the file,
27 resides in coreutils/.git) currently weighs in at about 30MB.  So you
52 is best recorded in your ~/.gitconfig file.  Edit that file, creating
53 it if needed, and put your name and email address in place of these
63 First of all, realize that to "commit" a change in git is a purely
65 in your current coreutils/ hierarchy.
79 The trouble with this approach is that you've just checked in a change
121     However, in any case, you will *not* lose your uncommitted changes.
122     Run "git stash" to temporarily hide uncommitted changes in your
134 put the ChangeLog entries *only* in the commit log, initially, unless
137 a step further, and no longer maintain an explicit ChangeLog file in
138 version control.  Instead, in a git working directory, you can view
143 So, you've committed a change.  But it's only in your local repository,
163 However, let's say there was one in ChangeLog, since you didn't
165 git rebase will tell you there was a conflict and in which
177 if there are conflicts in other files):
205 Do not modify any of the ChangeLog files in coreutils.  Starting in
208 and the commit log.  Now we put that information only in the commit log,
221 leading TABs that you're used to seeing in a "real" ChangeLog file, but
238 bug.  If you do that, add a note in your new commit log saying something
240 [bug introduced in coreutils-8.13] in the corresponding NEWS blurb.
241 Assuming you found the bug in commit 54cbe6e6, "git describe 54cbe6e6"
254 each has only one *line* in its body.
286 It is safe to omit the braces in the code above, since the
308 However, there is one exception in the other direction, when even a
350 Use SPACE-only indentation in all[*] files
352 We use space-only indentation in nearly all files.
366 directory name also matches, add the following in ~/.vimrc:
386 Send patches to the address listed in --help output
388 Please follow the guidelines in the "Sending your patches." section of
397 document it.  If you add an option, document it both in --help output
398 (i.e., in the usage function that generates the --help output) and in
401 are usually documented in NEWS, too.
416  mathematics background and perhaps a streak of something odd in their
430 If you must rearrange individual lines (e.g., in multi-line --help
444 Note to run tests/misc/new-test in isolation you can do:
458 There are hundreds of tests in the tests/ directories.  You can use
460 in tests/misc.
476 in Boston, the process can take a few weeks.
478 The forms to choose from are in gnulib's doc/Copyright/ directory.
512 induce no change in indentation.  Try not to add any more.
517 You may notice that the only trailing blanks in coreutils'
518 version-controlled files are in a single directory: tests/pr,
522 will alert you if you slip up, it's better to nip any problem in the
524 to configure your editor to highlight any offending characters in the
563   * git log: to get most of the same info in text form
569       change set, in a format suitable to be submitted and/or applied via
582         && for i in *; do git show $i|grep SOME_IDENTIFYING_STRING \
625 Texts.  A copy of the license is included in the "GNU Free