public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: git repository mirrors?
Date: Thu, 26 Jul 2007 15:11:00 -0000	[thread overview]
Message-ID: <87hcnrci9a.fsf@rho.meyering.net> (raw)
In-Reply-To: <20070726150322.GA30643@redhat.com> (Frank Ch. Eigler's message of "Thu\, 26 Jul 2007 11\:03\:22 -0400")

"Frank Ch. Eigler" <fche@redhat.com> wrote:
>> [...]  However, if sourceware has such infrastructure already in
>> place (or will soon), it'd make more sense to do it on the system
>> hosting the "upstream" repository.
>
> There is not git server daemon running, but some version of the git
> suite is installed.
>
> If you had shell access, you could in theory put a shared git repo
> somewhere under a project directory (/sourceware/projects/lvm2-home or
> /sourceware/www/sourceware/htdocs/lvm2) and export at least read-only
> http access to it.
>
> cgf, would it be hard to make your restricted-shell ssh wrapper to
> also accept git?

Thanks, but the http-hamstrung git isn't worth it: not nearly
as efficient, and rarely used, so probably not as robust.
IMHO, the only worthwhile way to allow read-only git access
is to open the git port, 9418.

If this is a hassle for you guys, don't worry.
I think I have all the pieces in place on et.redhat.com.

  reply	other threads:[~2007-07-26 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 13:07 Jim Meyering
2007-07-26 15:03 ` Frank Ch. Eigler
2007-07-26 15:11   ` Jim Meyering [this message]
2007-07-27  9:17   ` 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=87hcnrci9a.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=fche@redhat.com \
    --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).