unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Mathieu Lirzin <mthl@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] doc: Merge 'HACKING' into Texinfo manual.
Date: Wed, 10 Jun 2015 17:11:40 +0300	[thread overview]
Message-ID: <871thj8xgj.fsf@gmail.com> (raw)
In-Reply-To: <87eglj4ugc.fsf@openmailbox.org> (Mathieu Lirzin's message of "Wed, 10 Jun 2015 14:30:11 +0200")

Mathieu Lirzin (2015-06-10 15:30 +0300) wrote:

> Alex Kost <alezost@gmail.com> writes:
>
>> (Sorry for the delay).  I suppose it would be better not to push my
>> redundant patch.  Could you just add a line for 'help2man' to your
>> patch?
>
> Your patch is not related to the move, so IMO it would be more
> appropriate to keep a separate commit for your patch.

OK, the power is on your side this time :-) (Ludovic has pushed my patch)

>>> +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 ‘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.

Sorry, I didn't meant to force you to change that right away.  I'm
totally for discussion.

-- 
Alex

  reply	other threads:[~2015-06-10 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 11:42 [PATCH] doc: Merge 'HACKING' into Texinfo manual Mathieu Lirzin
2015-06-10  8:09 ` Ludovic Courtès
2015-06-10  8:21 ` Alex Kost
2015-06-10 12:30   ` Mathieu Lirzin
2015-06-10 14:11     ` Alex Kost [this message]
2015-06-10 19:52     ` Ludovic Courtès
2015-06-10 22:23       ` Mathieu Lirzin
2015-06-11 14:05         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871thj8xgj.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mthl@openmailbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).