From: Daniel Barkalow <barkalow@iabervon.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Non-http dumb protocols
Date: Sun, 1 Jul 2007 14:47:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707011444300.14638@iabervon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707011527590.4438@racer.site>
On Sun, 1 Jul 2007, Johannes Schindelin wrote:
> Hi,
>
> On Sat, 30 Jun 2007, Junio C Hamano wrote:
>
> > Having said that, I have a feeling that many people do not build
> > any of the commit walkers, and especially the http walker,
> > because they have no need for dumb protocols, and libcurl-dev is
> > just another piece of dependency they do not have to have.
>
> Interestingly, I just was involved in a discussion on IRC, where somebody
> (out of quotat concerns) wants to use sftp to push to a bare repository,
> which is served via HTTP.
>
> Unfortunately, it seems that all persons wanting to have some support for
> that, expect others to do the work for them.
>
> However, there is a miniscule non-zero chance that eventually somebody
> might want to realise an sftp push protocol (where you basically need the
> ls-remote part of the fetcher, too, to determine what to pack and send).
> And to complete a dumb sftp fetch protocol, you'd need a commit walker,
> so I'd like to have at least a minimal interface for commit walkers
> waiting for that saviour.
Okay, I think I'll go for ditching ssh-fetch/-push, making the
commit-walker code more modular, and possibly moving more of the smarts of
http-fetch into the common code so that local-fetch is a better test for
it and sftp fetch would be possible.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2007-07-01 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 20:19 Non-http dumb protocols Daniel Barkalow
2007-07-01 2:58 ` Junio C Hamano
2007-07-01 5:48 ` Julian Phillips
2007-07-01 14:32 ` Johannes Schindelin
2007-07-01 18:47 ` Daniel Barkalow [this message]
2007-07-01 20:53 ` Johannes Schindelin
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=Pine.LNX.4.64.0707011444300.14638@iabervon.org \
--to=barkalow@iabervon.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).