From: Chris Webb <chris@arachsys.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] Allow help.htmlpath to be an http: URL
Date: Wed, 27 Jun 2012 22:12:20 +0100 [thread overview]
Message-ID: <20120627211219.GD11498@arachsys.com> (raw)
In-Reply-To: <20120627210502.GB2292@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> > /* Check that we have a git documentation directory. */
> > - if (stat(mkpath("%s/git.html", html_path), &st)
> > - || !S_ISREG(st.st_mode))
> > - die(_("'%s': not a documentation directory."), html_path);
> > + if (prefixcmp(html_path, "http:")) {
> > + if (stat(mkpath("%s/git.html", html_path), &st)
> > + || !S_ISREG(st.st_mode))
> > + die("'%s': not a documentation directory.", html_path);
> > + }
>
> I'd rather not tie this directly to http. Is there any reason not to
> allow https, for example? Can we maybe just look for strstr("://")
> instead? That's the same magic we use to differentiate URLs from paths
> when looking for repositories.
Thanks, that's a much better heuristic! I'll use !strstr(html_path, "://")
in a re-roll. You're quite right, this ought to also allow https://, ftp://,
etc.
Best wishes,
Chris.
next prev parent reply other threads:[~2012-06-27 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 20:54 A handful of help-related patches Chris Webb
2012-06-27 20:55 ` [PATCH 1/3] Add config variable to set HTML path for git-help --web Chris Webb
2012-06-27 20:55 ` [PATCH 2/3] Allow help.htmlpath to be an http: URL Chris Webb
2012-06-27 21:05 ` Jeff King
2012-06-27 21:12 ` Chris Webb [this message]
2012-06-27 21:32 ` Junio C Hamano
2012-06-27 21:41 ` Chris Webb
2012-06-27 22:11 ` Jeff King
2012-06-27 22:19 ` Chris Webb
2012-06-27 22:52 ` Jeff King
2012-06-28 2:41 ` Junio C Hamano
2012-06-28 6:56 ` Chris Webb
2012-06-28 17:50 ` Jeff King
2012-06-28 23:39 ` Chris Webb
2012-06-27 20:55 ` [PATCH 3/3] Add a help format 'usage' to provide brief command usage Chris Webb
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=20120627211219.GD11498@arachsys.com \
--to=chris@arachsys.com \
--cc=git@vger.kernel.org \
--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).