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

Re: git commit -p? --loop?

From
SRSverre Rabbelier <alturin@gmail.com>
Date
Sep 3, 2008, 14:01 UTC
Message-ID
<bd6139dc0809030701y4a07c1a4secf08883235af9c0@mail.gmail.com>
In-Reply-To
<48BE4839.8080305@gmail.com>
On Wed, Sep 3, 2008 at 10:18, Ittay Dror <ittay.dror@gmail.com> wrote:
Show 5 quoted lines
> I find that many times I make changes to some files that should be part of
> different commits. What I do then is run 'git add -p' and 'git commit'
> several times until I commit all hunks. Does it make sense to anyone to add
> -p option following a '-a' and '--loop' option (that will run until user
> requests to end or nothing to commit)?
I wonder if "git commit --interactive" would not suit your needs?
-- 
Cheers,

Sverre Rabbelier
Previous: Ittay Dror
Message 2 of 2 in “git commit -p? --loop?”
  1. Ittay DrorSep 3, 2008
  2. Sverre RabbelierSep 3, 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.