git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Mark Wooding <mdw@distorted.org.uk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] daemon: Support a --user-path option.
Date: Fri, 03 Feb 2006 12:52:46 -0800	[thread overview]
Message-ID: <7vr76kcggx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060203202706.1895.70864.stgit@metalzone.distorted.org.uk> (Mark Wooding's message of "Fri, 03 Feb 2006 20:27:06 +0000")

Mark Wooding <mdw@distorted.org.uk> writes:

> If we're invoked with --user-path=FOO option, then a URL of the form
> git://~USER/PATH/... resolves to the path HOME/FOO/PATH/..., where HOME
> is USER's home directory.

I am probably slow as usual but I do not see how this is useful.

Wouldn't loosening the "request must be absolute if you use
--base-path" check in the area your first patch in the series
touches to also allow paths that start with a '~' be enough?
That way ~alice/foo would remain to be /home/alice/foo (with
/home/alice being alice's $HOME) and ~becky/bar would be
/home2/becky/bar (with /home2/becky being becky's $HOME).

I suppose you are doing something similar to ~/public_html, but
I think that is an independent feature.

  reply	other threads:[~2006-02-03 20:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 20:23 [PATCH 0/3] git-daemon hacking Mark Wooding
2006-02-03 20:27 ` [PATCH 1/3] daemon: Provide missing argument for logerror() call Mark Wooding
2006-02-03 20:27 ` [PATCH 2/3] daemon: Set SO_REUSEADDR on listening sockets Mark Wooding
2006-02-03 20:57   ` Junio C Hamano
2006-02-04  8:49   ` Junio C Hamano
2006-02-04 10:16     ` Mark Wooding
2006-02-03 20:27 ` [PATCH 3/3] daemon: Support a --user-path option Mark Wooding
2006-02-03 20:52   ` Junio C Hamano [this message]
2006-02-04  8:50     ` Junio C Hamano
2006-02-04 10:02     ` Mark Wooding
2006-02-04 12:40       ` Junio C Hamano
2006-02-04 19:13         ` Mark Wooding
2006-02-04 22:02           ` 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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=7vr76kcggx.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=mdw@distorted.org.uk \
    /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://80x24.org/mirrors/git.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).