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

Re: [RFC][RESEND][PATCH] Allow fetching from multiple repositories at once

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 23, 2006, 18:14 UTC
Message-ID
<Pine.LNX.4.63.0609232007550.25853@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20060923180539.GC20017@pasky.or.cz>
Hi,
On Sat, 23 Sep 2006, Petr Baudis wrote:
Show 36 quoted lines
>   Hi!
> 
> Dear diary, on Sat, Sep 23, 2006 at 07:54:10PM CEST, I got a letter
> where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
> > On Sat, 23 Sep 2006, Petr Baudis wrote:
> > 
> > > Dear diary, on Sat, Sep 23, 2006 at 07:23:01PM CEST, I got a letter
> > > where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
> > > > I still firmly believe that it would be way more efficient to fetch all 
> > > > those branches into _one_ proxy repository. Especially since you can reuse 
> > > > the objects with an alternate, which has an additional benefit over your 
> > > > approach.
> > > 
> > >   Huh? You can reuse the objects with my approach as well. Actually, it
> > > is automagically done so.
> > > 
> > >   With proxy repository, you would still need a server-side setup to
> > > maintain that repository, and specialized client-side porcelain to fetch
> > > from it. My approach initially requires some core changes (which aren't
> > > very pretty as it is but are not very fundamental or logically intrusive
> > > either) but in the longer run it pays off since you don't need a
> > > convoluted server-side setup for that.
> > 
> > No, you do not need _any_ server-side setup. And you do not need any 
> > specialized client-side porcelain other than a script, which just does 
> > the job.
> 
>   So how should the proxy repository be set up at the server side? I can
> just imagine a cronjob periodically sweeping the repositories and
> populate the proxy repository with new stuff (refs and objects) from
> those.
> 
>   Looking at what you wrote again, you talk about fetching all those
> branches _into_ one proxy repository. Perhaps we misunderstand each
> other. This patch is not about the "into" part, it is about being able
> to fetch _FROM_ _multiple_ repositories.
Indeed, I misunderstood.

Hmmm. Did you test if this makes things better? If so, could you test with one proxy repo on the server? I bet that this would be even more efficient.

And the proxy repo would be updated best by a hook, not a cronjob.

The thing is, your patch optimizes for a very special case, which special case IMHO should be handled differently to begin with.

Ciao, Dscho

Previous: Petr BaudisNext: Petr Baudis
Message 8 of 13 in “Allow fetching from multiple repositories at once”
  1. Petr BaudisSep 23, 2006
  2. A Large Angry SCMSep 23, 2006
  3. Petr BaudisSep 23, 2006
  4. Johannes SchindelinSep 23, 2006
  5. Petr BaudisSep 23, 2006
  6. Johannes SchindelinSep 23, 2006
  7. Petr BaudisSep 23, 2006
  8. Johannes SchindelinSep 23, 2006
  9. Petr BaudisSep 23, 2006
  10. Junio C HamanoSep 23, 2006
  11. Petr BaudisSep 23, 2006
  12. Jakub NarebskiSep 23, 2006
  13. Petr BaudisSep 23, 2006

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.