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

Re: What's cooking in git.git (Aug 2009, #06; Sun, 30)

From
NENick Edelen <sirnot@gmail.com>
Date
Sep 1, 2009, 22:25 UTC
Message-ID
<c77435a80909011525m3a6e7917xe066d61f3863e615@mail.gmail.com>
In-Reply-To
<7viqg48nxi.fsf@alter.siamese.dyndns.org>
Show 11 quoted lines
> * ne/rev-cache (2009-08-21) 6 commits
>  . support for path name caching in rev-cache
>  . full integration of rev-cache into git, completed test suite
>  . administrative functions for rev-cache, start of integration into git
>  . support for non-commit object caching in rev-cache
>  . basic revision cache system, no integration or features
>  . man page and technical discussion for rev-cache
>
> Updated but seems to break upload-pack tests when merged to 'pu'; given
> what this series touches, breakages in that area are expected.
> May discard if a working reroll comes, to give it a fresh start.

I vaguely remember something concerning those tests when starting the project. I'm a bit disconnected from everything right now, but I'll try to get those fixed as soon as I can.

Previous: Peter HarrisNext: Junio C Hamano
Message 15 of 16 in “What's cooking in git.git (Aug 2009, #06; Sun, 30)”
  1. Junio C HamanoAug 31, 2009
  2. Johan HerlandAug 31, 2009
  3. stash --dwim safety (was Re: What's cooking in git.git (Aug 2009, #06; Sun, 30))Junio C Hamano, Sep 1, 2009
  4. Matthieu MoySep 1, 2009
  5. Jeff KingSep 1, 2009
  6. Junio C HamanoSep 2, 2009
  7. Jeff KingSep 2, 2009
  8. Johannes SchindelinSep 2, 2009
  9. Matthieu MoySep 2, 2009
  10. Peter KreftingSep 1, 2009
  11. Jakub NarebskiSep 1, 2009
  12. Junio C HamanoSep 1, 2009
  13. Jakub NarebskiSep 2, 2009
  14. Peter HarrisSep 2, 2009
  15. Nick EdelenSep 1, 2009
  16. Junio C HamanoSep 2, 2009

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.