git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Is there a reason to keep walker.c ?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 27, 2008, 20:46 UTC
Message-ID
<alpine.LSU.1.00.0801272045490.23907@racer.site>
In-Reply-To
<20080127204535.GA4702@glandium.org>
Hi,
On Sun, 27 Jan 2008, Mike Hommey wrote:
Show 5 quoted lines
> 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?

Ciao, Dscho

Previous: Mike HommeyNext: Mike Hommey
Message 2 of 8 in “Is there a reason to keep walker.c ?”
  1. Mike HommeyJan 27, 2008
  2. Johannes SchindelinJan 27, 2008
  3. Mike HommeyJan 27, 2008
  4. Jakub NarebskiJan 27, 2008
  5. Daniel BarkalowJan 27, 2008
  6. Mike HommeyJan 28, 2008
  7. http-push as a builtin ? (Was: Is there a reason to keep walker.c ?)Mike Hommey, Jan 28, 2008
  8. Daniel BarkalowJan 28, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.