git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: git@vger.kernel.org
Subject: Is there a reason to keep walker.c ?
Date: Sun, 27 Jan 2008 21:45:35 +0100	[thread overview]
Message-ID: <20080127204535.GA4702@glandium.org> (raw)

Hi,

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 ?

Cheers,

Mike

             reply	other threads:[~2008-01-27 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 20:45 Mike Hommey [this message]
2008-01-27 20:46 ` Is there a reason to keep walker.c ? Johannes Schindelin
2008-01-27 20:51   ` Mike Hommey
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=20080127204535.GA4702@glandium.org \
    --to=mh@glandium.org \
    --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).