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

Re: [PATCH] reflog expire: add progress output

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Sep 21, 2018, 02:17 UTC
Message-ID
<CAPig+cSP6mSKYoEMwaSZjZTj-kiQUHukjPUXVh3tv8ySVtJd6A@mail.gmail.com>
In-Reply-To
<20180919141016.27930-1-avarab@gmail.com>

On Wed, Sep 19, 2018 at 10:10 AM Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

Show 6 quoted lines
> Before this change the "git reflog expire" command didn't report any
> progress. This is the second command (after "pack-refs --all --prune")
> that the "gc" command will run.
> [...]
> That may just be some artifact of the repositories I've tested, but I
> suspect It'll be true in general. As the callstack above shows, in
s/It'll/it'll/
> order to guarantee that we don't do that we'd need to pass some
> "progress" variable through 10 levels of functions, many of which are
> "for_each" callback functions with void* cb_data.
Previous: Duy Nguyen
Message 7 of 7 in “reflog expire: add progress output”
  1. reflog expire: add progress outputÆvar Arnfjörð Bjarmason, Sep 19, 2018
  2. Duy NguyenSep 19, 2018
  3. Ævar Arnfjörð BjarmasonSep 19, 2018
  4. Jeff KingSep 19, 2018
  5. Ævar Arnfjörð BjarmasonSep 19, 2018
  6. Duy NguyenSep 20, 2018
  7. Eric SunshineSep 21, 2018

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.