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

Re: merge vs rebase: Is visualization in gitk the only problem?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 27, 2007, 12:33 UTC
Message-ID
<Pine.LNX.4.64.0710271332030.4362@racer.site>
In-Reply-To
<CEA39C15-F9AE-46F5-BBE9-3F7AB0711494@zib.de>
Hi,
On Sat, 27 Oct 2007, Steffen Prohaska wrote:
> Could we somehow send rerere information together with a patch? This 
> would give the upstream maintainer (and everyone else who wants to test 
> the patch) the help needed to do a merge.

IMHO this is not sensible to send over email. But think I that something like this could be done for pullers: they fetch from somewhere, and then recreate the rerere information from the merge commits they just got (this would have to be a new option to git-rerere, methinks).

Ciao, Dscho

Previous: Steffen ProhaskaNext: Daniel Barkalow
Message 4 of 5 in “merge vs rebase: Is visualization in gitk the only problem?”
  1. Steffen ProhaskaOct 27, 2007
  2. David SymondsOct 27, 2007
  3. Steffen ProhaskaOct 27, 2007
  4. Johannes SchindelinOct 27, 2007
  5. Daniel BarkalowOct 27, 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.