From: Mike Hommey <mh@glandium.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Is there a reason to keep walker.c ?
Date: Sun, 27 Jan 2008 21:51:55 +0100 [thread overview]
Message-ID: <20080127205155.GA5476@glandium.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0801272045490.23907@racer.site>
On Sun, Jan 27, 2008 at 08:46:59PM +0000, Johannes Schindelin wrote:
> Hi,
>
> On Sun, 27 Jan 2008, Mike Hommey wrote:
>
> > While working on the http code refactoring, I got to wonder if the
> > walker.c "wrapper", that is only used for the http transport, is still
> > worth keeping. If there are plans for others transport to use this code,
> > obviously, it would be worth keeping, but on the contrary, I think it
> > would simplify the http transport code even more. What do you think ?
>
> Really, I was waiting for somebody needing ftp and/or sftp support badly
> enough, so let's keep it.
>
> I mean, one of those guys asking for ftp push support _got_ to just start
> scratching that itch, right?
Though, technically, ftp push could work with the curl code.
Mike
next prev parent reply other threads:[~2008-01-27 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 20:45 Is there a reason to keep walker.c ? Mike Hommey
2008-01-27 20:46 ` Johannes Schindelin
2008-01-27 20:51 ` Mike Hommey [this message]
2008-01-27 21:23 ` Jakub Narebski
2008-01-27 21:23 ` Daniel Barkalow
2008-01-28 7:17 ` Mike Hommey
2008-01-28 18:58 ` http-push as a builtin ? (Was: Is there a reason to keep walker.c ?) Mike Hommey
2008-01-28 19:45 ` Daniel Barkalow
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=20080127205155.GA5476@glandium.org \
--to=mh@glandium.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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).