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

Re: Alternative to manual editing with git add --patch

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 14, 2015, 16:52 UTC
Message-ID
<1326b047519c9398a0a06e27a26295ca@dscho.org>
In-Reply-To
<561E6FBB.7060302@gmx.de>
Hi Sven,
On 2015-10-14 17:07, Sven Helmberger wrote:
> 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.
How about implementing it and then discussing the implementation? That would have two advantages:
1) there would be something tangential to discuss, and
2) even if Junio rejects it, you can carry the patch in your private fork and use it forever.

Ciao, Johannes

Previous: Matthieu MoyNext: Junio C Hamano
Message 3 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.