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

Re: 'git diff' in rebase--interactive

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Oct 9, 2007, 12:35 UTC
Message-ID
<470B7581.3030301@viscovery.net>
In-Reply-To
<Pine.LNX.4.64.0710091319400.4174@racer.site>
Johannes Schindelin schrieb:
Show 7 quoted lines
> On Tue, 9 Oct 2007, Johannes Sixt wrote:
> 
>> I wonder for what reason rebase--interactive generates a patch using 
>> 'git diff' in the make_patch function. Is this an artefact?
> 
> It was an explicit request by people who use git-rebase regularly, and 
> missed being able to see the patch in --interactive.

Can we generate the patch with plumbing, diff-{files,index,tree}? They by-pass any diff drivers.

Show 5 quoted lines
>> I'd like to get rid of this use of 'git diff' because it invokes 
>> external diff drivers, which is totally unwanted if the driver is 
>> interactive - like the 'windiff' thing that I posted a week ago.
> 
> So you do not want to be able to run git-rebase (without -i)?

It wouldn't work anyway in my use-case (versioned Word documents), but rebase -m and rebase -i could run without manual intervention as long as there are no content merges.

In this particular case, I only wanted to amend the message of a commit 3 steps down in the history, and I had not expected any diff drivers to be fired up.

-- Hannes
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 3 of 5 in “'git diff' in rebase--interactive”
  1. Johannes SixtOct 9, 2007
  2. Johannes SchindelinOct 9, 2007
  3. Johannes SixtOct 9, 2007
  4. rebase -i: use diff plumbing instead of porcelainJohannes Schindelin, Oct 9, 2007
  5. Johannes SixtOct 9, 2007

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.