From: Scott Chacon <schacon@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Michael Norman <mwnorman@gmail.com>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: SVN support at GitHub (was Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?)
Date: Wed, 5 May 2010 08:08:21 -0700 [thread overview]
Message-ID: <w2md411cc4a1005050808q96802cfavbfd8ace700de1773@mail.gmail.com> (raw)
In-Reply-To: <vpqaaseqty8.fsf_-_@bauges.imag.fr>
Hey,
On Wed, May 5, 2010 at 7:55 AM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Scott Chacon <schacon@gmail.com> writes:
>
>> You can use GitHub for native SVN and Git access, both over http -
>> that will allow you to use Git as the main repository as it should be.
>> :)
>
> Wow, that's neat!
>
> Is it a private GitHub thing, or some open source code that other
> people can install on their own server?
>
Right now our version is very tied to our weird infrastructure, and
thus would not be generally useful, but I would like to fix and open
source it someday. Currently it's not much different than the HeeChee
project, however, which does largely the same thing, but for both Hg
and Git. If you're interested, I would check that out:
http://bitbucket.org/andrewgodwin/heechee/
Scott
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
>
next prev parent reply other threads:[~2010-05-05 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 14:10 Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too? Michael Norman
2010-05-05 14:16 ` Shawn O. Pearce
2010-05-05 14:20 ` Michael Norman
2010-05-05 14:32 ` Scott Chacon
2010-05-05 14:55 ` SVN support at GitHub (was Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?) Matthieu Moy
2010-05-05 15:08 ` Scott Chacon [this message]
2010-05-05 14:33 ` Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too? Nicolas Pitre
2010-05-06 12:04 ` Florian Weimer
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=w2md411cc4a1005050808q96802cfavbfd8ace700de1773@mail.gmail.com \
--to=schacon@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=mwnorman@gmail.com \
--cc=spearce@spearce.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).