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

Re: What's cooking in git.git (Jan 2010, #08; Sun, 24)

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 25, 2010, 23:47 UTC
Message-ID
<7vfx5t3fxo.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100125231241.GA4159@machine.or.cz>
Petr Baudis <pasky@suse.cz> writes:
Show 9 quoted lines
> ... I think
> it's healthier for new gitweb stuff to develop more in-tree, even
> if that means few angry users annoyed about less-than-perfect UI stuff,
> rather than polish the diamond in infinite discussions; worse is better!
> The only thing we should be worried about is avoiding introducing new
> bad URL interfaces since we should keep backwards compatibility there.
> ...
> For the main caching patch, it seems like good idea to take Jakub's
> split-up series instead, let's see what is J.H.'s opinion on the series?
Sounds reasonable.
Previous: Petr BaudisNext: Jakub Narebski
Message 6 of 9 in “What's cooking in git.git (Jan 2010, #08; Sun, 24)”
  1. Junio C HamanoJan 25, 2010
  2. Issues that need to be resolved before 1.7.0-rc1Junio C Hamano, Jan 25, 2010
  3. Johannes SixtJan 25, 2010
  4. Jakub NarebskiJan 25, 2010
  5. Petr BaudisJan 25, 2010
  6. Junio C HamanoJan 25, 2010
  7. Jakub NarebskiJan 26, 2010
  8. J.H.Jan 26, 2010
  9. Jakub NarebskiJan 26, 2010

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.