From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [PATCH] doc: Merge 'HACKING' into Texinfo manual.
Date: Wed, 10 Jun 2015 21:52:06 +0200
Message-ID: <87pp53fijd.fsf@gnu.org>
References: <87mw09xg4z.fsf@openmailbox.org> <877frcdlea.fsf@gmail.com>
	<87eglj4ugc.fsf@openmailbox.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60915)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1Z2m2m-0007nf-9W
	for guix-devel@gnu.org; Wed, 10 Jun 2015 15:52:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1Z2m2j-0004O8-UX
	for guix-devel@gnu.org; Wed, 10 Jun 2015 15:52:12 -0400
In-Reply-To: <87eglj4ugc.fsf@openmailbox.org> (Mathieu Lirzin's message of
	"Wed, 10 Jun 2015 14:30:11 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Mathieu Lirzin <mthl@openmailbox.org>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>

Mathieu Lirzin <mthl@openmailbox.org> skribis:

> Alex Kost <alezost@gmail.com> writes:

[...]

>>> +Modules that deal with the broader GNU system should be in the
>>> +@code{(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 =E2=80=98guix.texi=E2=
=80=99, 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=E2=80=99s proba=
bly
not used it consistently in the rest of the manual.)  It=E2=80=99s 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=C4=B1rl=C4=B1/Kammer" name?

Good question, I=E2=80=99m not sure.  Taylan?

> From 624e5e248f23563c8fb98e82d6c2bd5f25531e6c Mon Sep 17 00:00:00 2001
> From: Mathieu Lirzin <mthl@openmailbox.org>
> 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=E2=80=99.