git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Clemens Buchacher <drizzd@aon.at>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: [RFH] 'man:' macro for asciidoc
Date: Sat, 03 Mar 2012 10:33:36 -0800 (PST)	[thread overview]
Message-ID: <m31up9v8jo.fsf_-_@localhost.localdomain> (raw)
In-Reply-To: <20120303174252.GC28602@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:
> On Sat, Mar 03, 2012 at 03:50:53PM +0100, Clemens Buchacher wrote:

> >  http.proxy::
> > -	Override the HTTP proxy, normally configured using the 'http_proxy'
> > -	environment variable (see linkgit:curl[1]).  This can be overridden
> > -	on a per-remote basis; see remote.<name>.proxy
> > +	Override the HTTP proxy, normally configured using the 'http_proxy',
> > +	'https_proxy', and 'all_proxy' environment variables (see
> > +	linkgit:curl[1]).  This can be overridden on a per-remote basis; see
> > +	remote.<name>.proxy
> 
> Text looks OK. I think this linkgit:curl is wrong, though. In the
> manpages, it formats as simply curl(1), but in the HTML pages, it
> creates a link to curl.html, which does not exist. This is not a problem
> introduced by your patch, obviously, but maybe it is worth cleaning up.
> I think just using:
> 
>   `curl(1)`
> 
> might be sufficient.

BTW it wouldreally be nice be able to use simply  man:curl[1]  instead
of worrying if it shoudl be `curl(1)`, or *curl*(1), or curl(1)


-- 
Jakub Narebski

  reply	other threads:[~2012-03-03 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 14:50 [PATCH] http.proxy: also mention https_proxy and all_proxy Clemens Buchacher
2012-03-03 17:42 ` Jeff King
2012-03-03 18:33   ` Jakub Narebski [this message]
2012-03-03 22:22   ` Junio C Hamano
2012-03-04 12:46     ` Clemens Buchacher
2012-03-04 23:07       ` Junio C Hamano
2012-03-04 16:50   ` [PATCH v2] " Clemens Buchacher
2012-03-05  5:11     ` Junio C Hamano

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

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

  git send-email \
    --in-reply-to=m31up9v8jo.fsf_-_@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=drizzd@aon.at \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.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.
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 NNTP newsgroup(s).