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

Re: linux-next: stackprotector tree build failure

From
SRStephen Rothwell <sfr@canb.auug.org.au>
Date
Oct 22, 2008, 23:54 UTC
Message-ID
<20081023105454.880e13e2.sfr@canb.auug.org.au>
In-Reply-To
<alpine.DEB.1.00.0810221908100.22125@pacific.mpi-cbg.de.mpi-cbg.de>
Hi Johannes,
On Wed, 22 Oct 2008 19:41:18 +0200 (CEST) Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
> I think it might be in order to explain how git-rerere works internally:
Thanks for the explanation.
> So I think that you might hit the unfortunate case where two files 
> happened to have the same conflicts, but you needed to resolve them one 
> way for one file, and another way for the other file.
Which makes perfect sense, unfortunately.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
Previous: Johannes Schindelin
Message 6 of 6 in “Re: linux-next: stackprotector tree build failure”
  1. Ingo MolnarOct 22, 2008
  2. Stephen RothwellOct 22, 2008
  3. Stephen RothwellOct 22, 2008
  4. Ingo MolnarOct 22, 2008
  5. Johannes SchindelinOct 22, 2008
  6. Stephen RothwellOct 22, 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.