From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Non-http dumb protocols
Date: Sun, 1 Jul 2007 21:53:33 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707012153190.4438@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0707011444300.14638@iabervon.org>
Hi,
On Sun, 1 Jul 2007, Daniel Barkalow wrote:
> 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.
Thanks,
Dscho
prev parent reply other threads:[~2007-07-01 20:53 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
2007-07-01 20:53 ` Johannes Schindelin [this message]
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.0707012153190.4438@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--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).