Files
git/Documentation
Junio C Hamano ff5507ed2a Documentation/config.txt: describe the structure first and then meaning
A line can be continued via a backquote-LF and can be chomped at a
comment character.  But that is not specific to string-typed values.
It is common to all, just like unquoted leading and trailing
whitespaces are stripped and inter-word spacing are retained.

Move the description around and desribe these structural rules
first, then introduce the double-quote facility as a way to override
them, and finally mention various types of values.

Note that these structural rules only apply to the value part of the
configuration file.  E.g.

    [aSection] \
        name \
	= value

does not work, because the rules kick in only after seeing "name =".
Both the original and the updated text are phrased in an awkward way
by singling out the "value" part of the line because of this.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-03-04 11:42:34 -08:00
..
2014-12-17 11:18:45 -08:00
2013-07-22 16:06:48 -07:00
2013-02-14 10:29:01 -08:00
2013-09-17 11:42:51 -07:00
2013-09-04 12:23:25 -07:00
2012-06-19 11:35:19 -07:00
2013-09-09 14:50:36 -07:00
2013-10-23 13:21:31 -07:00
2013-09-17 11:42:51 -07:00
2011-09-06 11:42:12 -07:00
2013-05-29 14:23:04 -07:00
2013-04-12 12:00:52 -07:00
2013-10-18 13:50:12 -07:00
2011-03-11 10:59:16 -05:00
2013-04-12 12:00:52 -07:00
2014-12-17 11:18:45 -08:00
2013-10-22 11:23:31 -07:00
2013-06-09 13:45:32 -07:00
2013-07-22 16:06:48 -07:00
2013-09-20 12:38:10 -07:00
2013-09-17 11:42:54 -07:00