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

Re: [PATCH] git-commit: '--no-status' Allow suppression of status summary in commit msg

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 28, 2008, 19:09 UTC
Message-ID
<7vd4jtdki8.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1219949215-10189-1-git-send-email-marcus@griep.us>
Marcus Griep <marcus@griep.us> writes:
Show 5 quoted lines
> Currently, using any editor to edit a commit message for 'git commit'
> kicks of a 'git status' which is then included as comments to give
> the commit author some context. However, in some situations, such as
> having a working tree of many hundred thousand files or on an inefficient
> filesystem,

I am not interested in this particular patch, especially the part that hoards a short-and-nice -S flag that we could use for something more useful. Also calling the configuration variable "nostatus" is backwards; I'd name it to "showstatus" that defaults to "true" if I were doing this.

You did not mention exactly how the "hundred thousand files on an inefficient filesystem" is a problem, but if it is about listing untracked files, I thought Marius Storm-Olsen added a feature to address that with 4bfee30 (Add an optional <mode> argument to commit/status -u|--untracked-files option, 2008-06-05).

If that is not still enough for your particular use case, I think you can have a custom wrapper that does:

	#!/bin/sh
	: >.log-message-file &&
        vi .log-message-file &&
        git commit -F .log-message-file "$@" &&
        rm -f .log-message-file 
without touching git at all.
Previous: Marcus GriepNext: Alex Riesen
Message 2 of 7 in “git-commit: '--no-status' Allow suppression of status summary in commit msg”
  1. git-commit: '--no-status' Allow suppression of status summary in commit msgMarcus Griep, Aug 28, 2008
  2. Junio C HamanoAug 28, 2008
  3. Alex RiesenAug 28, 2008
  4. Alex RiesenAug 28, 2008
  5. Marcus GriepAug 28, 2008
  6. Marius Storm-OlsenAug 29, 2008
  7. Marius Storm-OlsenAug 29, 2008

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.