Re: git patch

From: Junio C Hamano <junkio@cox.net>
Date: Dec 6, 2006, 10:00 UTC
Message-ID: <7vslft738m.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <4576937D.1070402@xs4all.nl>

Han-Wen Nienhuys <hanwen@xs4all.nl> writes:

Show 12 quoted lines

> I think it would be more logical to show those diffs as part of
> git-status and perhaps git-commit, eg.
>
>   git-commit --dry-run <commitoptions>
>
> shows the diff of what would be committed
>
>   git-status --diff
>
> shows diffs of modified files in the working tree.
>
> This makes it more clear what each diff means.

Just in case people did not know, "git status" is pronounced as "git commit --dry-run".

It takes exactly the same set of parameters as "git commit", and shows what would have been in the commit log message editor as the status comments.

And it even takes the "-v" option that "git commit" takes.

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