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

Re: What's cooking in git.git (topics)

From
Daniel Barkalow <barkalow@iabervon.org>
Date
May 14, 2007, 03:21 UTC
Message-ID
<Pine.LNX.4.64.0705132234001.18541@iabervon.org>
In-Reply-To
<Pine.LNX.4.64.0705140121030.5520@beast.quantumfyre.co.uk>
On Mon, 14 May 2007, Julian Phillips wrote:
Show 18 quoted lines
> On Sun, 13 May 2007, Junio C Hamano wrote:
> 
> > Thanks for the status updates.  Although I do not recall Daniel
> > saying it explicitly, I have been assuming that his series was
> > aiming for the same all along.  It might be a good idea for you
> > two to compare notes sometime between now and v1.5.2?
> 
> Well, it can't be a bad idea, can it? ;)
> 
> Apart from the code itself (which can be found at
> http://git.q42.co.uk/w/fetch2.git), I don't have any actual notes, and since I
> haven't had a chance to work on it for a couple of weeks I'm not 100% sure of
> where I was at - due to lack of time I have tended to just spend a few hours
> adding some missing part when I found the time but I don't actually have a
> TODO list or similar (though I really should).
> 
> I'm also out of town with work for the first half of the coming week ... but
> I'm certainly willing to talk about what I have and haven't done.

I've actually been largely unsuccessful in figuring out how to do most of the fetch logic in C, but I was expecting that somebody would write it if the library were available.

I've been working on various little things that are a lot easier if the parsing is centralized:

 * update tracking refs on push
 * handle refspec patterns in match_refs so that send-pack/http-push can 
   take them and builtin-push doesn't need to do anything, and can also
   turn --tags into +refs/tags/*:refs/tags/*.

I've also been looking at doing something like your remote_ops, but also including something for push, and doing it in another library file (so push, fetch, and ls-remote can all share the same dispatch on type of url).

> (Daniel, hope you don't mind me adding you to CC ...)

Not at all; I hadn't noticed this thread yet, and it's quite related to what I'm working on.

	-Daniel
*This .sig left intentionally blank*
Previous: Julian PhillipsNext: Junio C Hamano
Message 5 of 34 in “What's cooking in git.git (topics)”
  1. Junio C HamanoMay 13, 2007
  2. Julian PhillipsMay 13, 2007
  3. Junio C HamanoMay 13, 2007
  4. Julian PhillipsMay 14, 2007
  5. Daniel BarkalowMay 14, 2007
  6. Junio C HamanoMay 17, 2007
  7. Daniel BarkalowMay 17, 2007
  8. Junio C HamanoMay 17, 2007
  9. Daniel BarkalowMay 17, 2007
  10. Junio C HamanoMay 19, 2007
  11. Junio C HamanoMay 23, 2007
  12. Shawn O. PearceMay 24, 2007
  13. Junio C HamanoMay 29, 2007
  14. Junio C HamanoJun 2, 2007
  15. Johannes SchindelinJun 3, 2007
  16. Shawn O. PearceJun 3, 2007
  17. Nicolas PitreJun 3, 2007
  18. Dana HowJun 3, 2007
  19. Junio C HamanoJun 7, 2007
  20. Junio C HamanoJun 13, 2007
  21. Johannes SchindelinJun 13, 2007
  22. Linus TorvaldsJun 14, 2007
  23. Matthias LederhoferJun 18, 2007
  24. Junio C HamanoJun 21, 2007
  25. Linus TorvaldsJun 21, 2007
  26. Linus TorvaldsJun 21, 2007
  27. Junio C HamanoJun 25, 2007
  28. Jeffrey C. OllieJun 25, 2007
  29. Matthias LederhoferJun 26, 2007
  30. Junio C HamanoJun 27, 2007
  31. Matthias LederhoferJun 28, 2007
  32. Junio C HamanoJun 29, 2007
  33. Junio C HamanoJul 2, 2007
  34. Junio C HamanoJul 28, 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.