mirror of
https://git.savannah.gnu.org/git/bison.git
synced 2026-03-09 12:23:04 +00:00
global: remove unnecessary horizontal tabs.
This change was made by applying emacs' untabify function to nearly all files in Bison's repository. Required tabs in make files, ChangeLog, regexps, and test code were manually skipped. Other notable exceptions and changes are listed below. * bootstrap: Skip because we sync this with gnulib. * data/m4sugar/foreach.m4 * data/m4sugar/m4sugar.m4: Skip because we sync these with Autoconf. * djgpp: Skip because I don't know how to test djgpp properly, and this code appears to be unmaintained anyway. * README-hacking (Hacking): Specify that tabs should be avoided where not required.
This commit is contained in:
16
ChangeLog
16
ChangeLog
@@ -1,3 +1,19 @@
|
||||
2011-07-24 Joel E. Denny <joeldenny@joeldenny.org>
|
||||
|
||||
global: remove unnecessary horizontal tabs.
|
||||
This change was made by applying emacs' untabify function to
|
||||
nearly all files in Bison's repository. Required tabs in make
|
||||
files, ChangeLog, regexps, and test code were manually skipped.
|
||||
Other notable exceptions and changes are listed below.
|
||||
* bootstrap: Skip because we sync this with gnulib.
|
||||
* data/m4sugar/foreach.m4
|
||||
* data/m4sugar/m4sugar.m4: Skip because we sync these with
|
||||
Autoconf.
|
||||
* djgpp: Skip because I don't know how to test djgpp properly, and
|
||||
this code appears to be unmaintained anyway.
|
||||
* README-hacking (Hacking): Specify that tabs should be avoided
|
||||
where not required.
|
||||
|
||||
2011-07-10 Joel E. Denny <joeldenny@joeldenny.org>
|
||||
|
||||
build: avoid YACC typo inherited from Autoconf.
|
||||
|
||||
@@ -46,6 +46,13 @@ of the .output file etc. This excludes impossible error messages
|
||||
(comparable to assert/abort), and all the --trace output which is
|
||||
meant for the maintainers only.
|
||||
|
||||
** Horizontal tabs
|
||||
Do not add horizontal tab characters to any file in Bison's repository
|
||||
except where required. For example, do not use tabs to format C code.
|
||||
However, make files, ChangeLog, and some regular expressions require
|
||||
tabs. Also, test cases might need to contain tabs to check that Bison
|
||||
properly processes tabs in its input.
|
||||
|
||||
|
||||
* Working from the repository
|
||||
|
||||
|
||||
Reference in New Issue
Block a user