From: Andreas Ericsson <ae@op5.se>
To: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH 0/4] User-relative paths, take two.
Date: Tue, 01 Nov 2005 23:44:53 +0100 [thread overview]
Message-ID: <4367EFE5.8070009@op5.se> (raw)
I've reworked the user-relative paths according to the discussion "[RFC]
GIT paths" started by Junio. In addition I've added a '--strict-paths'
option to git-daemon.
I think I got everything right. At least it builds nicely and works as
expected.
Comments welcome. Upstream inclusion even more so. :)
Btw. I'll have some more patches for git-daemon soon (--server-root and
--userdir) which will rely on these patches making it in. Should I hold
off on that for now?
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
reply other threads:[~2005-11-01 22:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4367EFE5.8070009@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.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.
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).