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

Alternative to manual editing with git add --patch

From
Sven Helmberger <sven.helmberger@gmx.de>
Date
Oct 14, 2015, 15:07 UTC
Message-ID
<561E6FBB.7060302@gmx.de>
Hello,
I hope this hasn't been discussed before.

I'm a big fan of cleanliness in commits and therefore often use git add --patch to sort code changes I made into the right commits etc.

What I then often encountered was the situation where I happened to have inserted consecutive lines of code that conceptually belong to different commits. Normally I can nicely split patches, but not in this case, making manually editing the patch the only alternative.

Shouldn't there be at least a way to quickly say line-by-line if you want to have it added or not?

Personally, I find manually editing just annoying, it seems overly arcane, but it also prevents me from really recommending "add --patch" as best practice. I think it's a really good idea for many reasons to do so, but I can't really tell people already struggling with using git that I expect them to edit patches manually.

Regards, Sven Helmberger

Next: Matthieu Moy
Message 1 of 9 in “Alternative to manual editing with git add --patch”
  1. Sven HelmbergerOct 14, 2015
  2. Matthieu MoyOct 14, 2015
  3. Johannes SchindelinOct 14, 2015
  4. Junio C HamanoOct 14, 2015
  5. Sven HelmbergerOct 14, 2015
  6. Johannes SchindelinOct 15, 2015
  7. Sven HelmbergerOct 15, 2015
  8. Johannes SchindelinOct 15, 2015
  9. Sven HelmbergerOct 15, 2015

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.