From: "Frank Ch. Eigler" <fche@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: overseers@sourceware.org
Subject: Re: a sourceware git server?
Date: Wed, 19 Sep 2007 11:19:00 -0000 [thread overview]
Message-ID: <20070919111918.GF8765@redhat.com> (raw)
In-Reply-To: <87k5qn3y7y.fsf@rho.meyering.net>
Hi -
On Wed, Sep 19, 2007 at 09:34:25AM +0200, Jim Meyering wrote:
> [...]
> This will fix it:
> chgrp lvm /git/lvm2.git/.
Done.
> These work fine:
> git-clone ssh://sourceware.org/git/dm
> git-clone git://sourceware.org/git/dm
>
> But these slightly shorter commands don't work:
> git-clone ssh://sourceware.org/dm
> git-clone git://sourceware.org/dm
That's because I wanted to keep the ssh: and git: URLs the same.
> [...] you can add the --base-path=/git option in xinet.d.
AFAIK, that would only affect the git: URL, and force the ssh: one to
contain the base path name (/git).
- FChE
next prev parent reply other threads:[~2007-09-19 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 18:32 Jim Meyering
2007-09-19 2:55 ` Frank Ch. Eigler
2007-09-19 7:34 ` Jim Meyering
2007-09-19 11:19 ` Frank Ch. Eigler [this message]
2007-09-19 11:35 ` Jim Meyering
-- strict thread matches above, loose matches on Subject: below --
2007-09-18 17:31 Jim Meyering
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=20070919111918.GF8765@redhat.com \
--to=fche@redhat.com \
--cc=jim@meyering.net \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).