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

Re: logging disjoint sets of commits in a single command

From
Jeff King <peff@peff.net>
Date
Feb 1, 2012, 03:03 UTC
Message-ID
<20120201030300.GA9969@sigill.intra.peff.net>
In-Reply-To
<CB4DCD5C.747%bryano@fb.com>
On Wed, Feb 01, 2012 at 01:02:57AM +0000, Bryan O'Sullivan wrote:
Show 6 quoted lines
> By the way, the reason I'm even interested in this in the first place is
> that the performance of commands like "git blame" and "git log" on files
> and subtrees has become a problem for us (> 10 seconds per invocation,
> forecast to get much worse), and I wanted to see whether I could feed "git
> log" a specific list of revisions, and if so, whether that could yield
> good performance.

That sounds kind of slow. Is your repository really gigantic? Have you packed everything? I'm just curious if there's some other way to make things faster. Is the repository publicly available?

-Peff
Previous: Bryan O'SullivanNext: Bryan O'Sullivan
Message 6 of 8 in “logging disjoint sets of commits in a single command”
  1. Bryan O'SullivanFeb 1, 2012
  2. Bryan O'SullivanFeb 1, 2012
  3. Carlos Martín NietoFeb 1, 2012
  4. Jeff KingFeb 1, 2012
  5. Bryan O'SullivanFeb 1, 2012
  6. Jeff KingFeb 1, 2012
  7. Bryan O'SullivanFeb 1, 2012
  8. Junio C HamanoFeb 1, 2012

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.