Re: [PATCH] doc: Merge 'HACKING' into Texinfo manual.

[Ludovic Courtès]

Mathieu Lirzin <address@hidden> skribis:

> Alex Kost <address@hidden> writes:

[...]

>>> +Modules that deal with the broader GNU system should be in the
>>> address@hidden(gnu ...)} name space rather than @code{(guix ...)}.
>>
>> I would use '@dots{}' instead of '...' there, although I see that the
>> real "hardcoded" dots are used in some places of ‘guix.texi’, so I don't
>> really know if we have a convention on that subject.
>
> I looked at the Texinfo manual, and I think '@dots{}' fill its purposes
> when used in text since it's referenced in "Glyphs for text" section.  I
> don't know if it's intended to be used in code snippets.  I have put
> this glyphs in my patch, but I think it would need more discussions.

I think @dots{} is appropriate in this case (even though it’s probably
not used it consistently in the rest of the manual.)  It’s basically
equivalent to inserting HORIZONTAL ELLIPSIS, which is what we want.

>>Yes, please.  (We may have to compress the copyright lines eventually
>>for the PS/PDF output.)
>
> Please check if it's ok for you. I used "MA"git-blame ;-) in order to
> adapt the copyright notices. How do we sort alphabetically "Taylan
> Ulrich Bayırlı/Kammer" name?

Good question, I’m not sure.  Taylan?

> From 624e5e248f23563c8fb98e82d6c2bd5f25531e6c Mon Sep 17 00:00:00 2001
> From: Mathieu Lirzin <address@hidden>
> Date: Wed, 10 Jun 2015 13:39:54 +0200
> Subject: [PATCH] doc: Move most 'HACKING' informations into the manual.
>
> * HACKING (Contributing): New section.
>   (Building from Git, The Perfect Setup, Coding Style, Submitting Patches):
>   Move to ...
> * doc/guix.texi (Running Guix Before It Is Installed): Likewise.
>   (Contributing): ... here.
> * README (Installation): Adapt to it.
> * configure.ac (DOT): Likewise.

LGTM, please push!

Ludo’.