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, 08:31 UTC
Message-ID
<20081022193113.20369b63.sfr@canb.auug.org.au>
In-Reply-To
<20081022192725.5f5de711.sfr@canb.auug.org.au>
On Wed, 22 Oct 2008 19:27:25 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
Show 5 quoted lines
>
> I think rerere matches preimages on the SHA1 of the conflict (or its
> reverse), so sufficiently similar pieces of code will match.  I would
> expect things like ext2/3/4 to be candidates.  Did the traps_32.c one
> match one for traps_64.c?

Or, of course similar conflicts in different merges in different branches of the same tree are really asking for it ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
Previous: Stephen RothwellNext: Ingo Molnar
Message 3 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.