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

Re: [PATCH 2/5] Refactor struct transport_ops inlined into struct transport

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 20, 2007, 10:59 UTC
Message-ID
<Pine.LNX.4.64.0709201159260.28395@racer.site>
In-Reply-To
<Pine.LNX.4.64.0709192226150.21941@iabervon.org>
Hi,
On Wed, 19 Sep 2007, Daniel Barkalow wrote:
Show 33 quoted lines
> On Wed, 19 Sep 2007, Johannes Schindelin wrote:
> 
> > On Wed, 19 Sep 2007, Shawn O. Pearce wrote:
> > 
> > > diff --git a/transport.c b/transport.c
> > > index cc76e3f..d8458dc 100644
> > > --- a/transport.c
> > > +++ b/transport.c
> > > @@ -44,8 +44,6 @@ static int disconnect_walker(struct transport *transport)
> > >  	return 0;
> > >  }
> > >  
> > > -static const struct transport_ops rsync_transport;
> > > -
> > >  static int curl_transport_push(struct transport *transport, int refspec_nr, const char **refspec, int flags) {
> > >  	const char **argv;
> > >  	int argc;
> > > @@ -431,18 +406,31 @@ struct transport *transport_get(struct remote *remote, const char *url)
> > >  	ret->url = url;
> > >  
> > >  	if (!prefixcmp(url, "rsync://")) {
> > > -		ret->ops = &rsync_transport;
> > > +		/* not supported; don't populate any ops */
> > > +
> > 
> > That is sneaky.  What are the reasons to remove rsync support?  I know it 
> > is deprecated, but I'd still like to have it, especially for initial 
> > clones on small-RAMed machines.
> 
> It never got implemented in a way called from C. This is just removing the 
> pointer to the empty struct where support would go. If anybody knows 
> enough about interfacing with rsync to write the necessary functions, it 
> can be restored.
Okay, will do once I find the time.

Ciao, Dscho

Previous: Daniel Barkalow
Message 4 of 4 in “Refactor struct transport_ops inlined into struct transport”
  1. 2/5 Refactor struct transport_ops inlined into struct transportShawn O. Pearce, Sep 19, 2007
  2. Johannes SchindelinSep 19, 2007
  3. Daniel BarkalowSep 20, 2007
  4. Johannes SchindelinSep 20, 2007

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.