unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 42214@debbugs.gnu.org
Subject: [bug#42214] [PATCH] doc: Fix texinfo identifiers in Version Control Services.
Date: Mon, 06 Jul 2020 14:43:12 +0200	[thread overview]
Message-ID: <87a70c7r1b.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20200705085156.9488-1-arunisaac@systemreboot.net> (Arun Isaac's message of "Sun, 5 Jul 2020 14:21:56 +0530")

Hello,

Arun Isaac <arunisaac@systemreboot.net> writes:

> * doc/guix.texi (Version Control Services): Use @code, @file, @indicateurl
> texinfo identifiers correctly.

Thank you. Some nit-picking follows.

> +If you run git daemon with @code{(base-path "/srv/git")} on example.com,

  Git daemon 

or

  @command{git daemon}

and

  @samp{example.com}

> +specified with empty string, requests to
> +@indicateurl{git://host/~alice/foo} is taken as a request to access
> +@code{foo} repository in the home directory of user @code{alice}.  If
> +@code{(user-path "path")} is specified, the same request is taken as a

Maybe

  @code{(user-path "@var{path}")}

> +request to access @file{path/foo} repository in the home directory of

and then @samp{@var{path}/foo}

> +Path prefix for Git access.  With the default @file{/git/} prefix, this

@samp{/git/}

> +will map @indicateurl{http://@var{server}/git/@var{repo}.git} to
> +@file{/srv/git/@var{repo}.git}.  Requests whose URI paths do not begin

In any case, it looks good.

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2020-07-06 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05  8:51 [bug#42214] [PATCH] doc: Fix texinfo identifiers in Version Control Services Arun Isaac
2020-07-06 12:43 ` Nicolas Goaziou [this message]
2020-07-06 15:53   ` bug#42214: " Arun Isaac

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=87a70c7r1b.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=42214@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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).