Re: [PATCH v3 7/7] revision.c: refactor basic topo-order logic

From: Stefan Beller <sbeller@google.com>
Date: Oct 11, 2018, 22:32 UTC
Message-ID: <CAGZ79kYttgMUeQk7fvXGk2+SF10PS8yqsgNH47HBQLfNqShpMQ@mail.gmail.com>
In-Reply-To: <020b2f50c5703e8291577b008fdfa567093c6eab.1537551564.git.gitgitgadget@gmail.com>

On Fri, Sep 21, 2018 at 10:39 AM Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com> wrote:

>
> From: Derrick Stolee <dstolee@microsoft.com>

[...]

Show 5 quoted lines

> For the test above, I specifically selected a path that is changed
> frequently, including by merge commits. A less-frequently-changed
> path (such as 'README') has similar end-to-end time since we need
> to walk the same number of commits (before determining we do not
> have 100 hits). However, get get the benefit that the output is

"get get"

$ 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.