On 02/21/2012 02:14 PM, Eric Blake wrote:
>
> Picking another character would work as a compromise. Even a line
> of '---' is a visual separator; only '<', '=', and '>' give me
> heartburn in the context of merge conflict resolution.
>
OK, I went for the "~" character, that is the one that pr
On 02/21/2012 06:05 AM, Stefano Lattarini wrote:
> On 02/21/2012 01:39 PM, Eric Blake wrote:
>> On 02/21/2012 05:34 AM, Stefano Lattarini wrote:
>>> * NEWS: Get rid of form-feed characters (^L) throughout the file.
>>> Use separator lines instead (composed by 76 '=' characters), or
>>> just an extr
On 02/21/2012 01:39 PM, Eric Blake wrote:
> On 02/21/2012 05:34 AM, Stefano Lattarini wrote:
>> * NEWS: Get rid of form-feed characters (^L) throughout the file.
>> Use separator lines instead (composed by 76 '=' characters), or
>> just an extra blank lines for older less verbose entries (those
>>
On 02/21/2012 05:34 AM, Stefano Lattarini wrote:
> * NEWS: Get rid of form-feed characters (^L) throughout the file.
> Use separator lines instead (composed by 76 '=' characters), or
> just an extra blank lines for older less verbose entries (those
> predating the 1.8 release).
Why?
I _like_ ^L a
* NEWS: Get rid of form-feed characters (^L) throughout the file.
Use separator lines instead (composed by 76 '=' characters), or
just an extra blank lines for older less verbose entries (those
predating the 1.8 release).
(New in 1.11.3): Move description of planned future backward
incompatibilitie
