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

Re: [PATCH] Recommend "git gc --prune=now" instead of "git prune"

From
Denton Liu <liu.denton@gmail.com>
Date
Jun 8, 2020, 10:17 UTC
Message-ID
<20200608101720.GA33389@generichostname>
In-Reply-To
<pull.652.git.1591581739031.gitgitgadget@gmail.com>
Hi John,
Thanks for working on this topic.
On Mon, Jun 08, 2020 at 02:02:18AM +0000, John Lin via GitGitGadget wrote:
> Subject: [PATCH] Recommend "git gc --prune=now" instead of "git prune"

The format for subjects is generally "<area>: <description>" so perhaps something like "git gc: recommend use of `git gc --prune=now`"?

> From: John Lin <johnlinp@gmail.com>
> 
> Signed-off-by: John Lin <johnlinp@gmail.com>

This commit is missing some justification. In the commit message, we should mention that `git prune` is a plumbing command and in the documentation for it, it mentions that the porcelain `git gc` command should be used instead.

Previous: John Lin via GitGitGadgetNext: John Lin via GitGitGadget
Message 2 of 9 in “Recommend "git gc --prune=now" instead of "git prune"”
  1. Recommend "git gc --prune=now" instead of "git prune"John Lin via GitGitGadget, Jun 8, 2020
  2. Denton LiuJun 8, 2020
  3. gc: recommend `git gc --prune=now` instead of `git prune`John Lin via GitGitGadget, Jun 9, 2020
  4. Junio C HamanoJun 9, 2020
  5. Ævar Arnfjörð BjarmasonJun 9, 2020
  6. Junio C HamanoJun 9, 2020
  7. 林自均Jun 10, 2020
  8. Denton LiuJun 10, 2020
  9. 林自均Jun 10, 2020

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.