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

Re: USE_SHA1DC is broken in pu

From
Lars Schneider <larsxschneider@gmail.com>
Date
Mar 17, 2017, 03:18 UTC
Message-ID
<2B1DE627-11C8-4FA5-A354-76B6C475666A@gmail.com>
In-Reply-To
<CA+55aFzJ3NFVoN6K9__nM_LWYfegxGo_YxB0OudTNBCG+qq+3Q@mail.gmail.com>
Show 10 quoted lines
> On 17 Mar 2017, at 03:22, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> I think there's a semantic merge error and it clashes with
> f18f816cb158 ("hash.h: move SHA-1 implementation selection into a
> header file").
> 
> Suggested possible merge resolution attached.
> 
>                   Linus
> <patch.diff>

Would it make sense/have value to add a job to our TravisCI build [1] that compiles Git in a few variations with some high profile switches such as USE_SHA1DC? Running all the tests for these variations would probably take to long but just compiling would be less than 2min per variation.

- Lars
[1] https://travis-ci.org/git/git/branches
Previous: Junio C HamanoNext: Lars Schneider
Message 8 of 18 in “USE_SHA1DC is broken in pu”
  1. Linus TorvaldsMar 16, 2017
  2. Jeff KingMar 16, 2017
  3. Linus TorvaldsMar 16, 2017
  4. Junio C HamanoMar 16, 2017
  5. Linus TorvaldsMar 16, 2017
  6. Linus TorvaldsMar 16, 2017
  7. Junio C HamanoMar 16, 2017
  8. Lars SchneiderMar 17, 2017
  9. Lars SchneiderMar 17, 2017
  10. Johannes SchindelinMar 21, 2017
  11. Junio C HamanoMar 21, 2017
  12. Johannes SchindelinMar 22, 2017
  13. Jonathan NiederMar 22, 2017
  14. Johannes SchindelinMar 23, 2017
  15. Linus TorvaldsMar 23, 2017
  16. Jeff KingMar 23, 2017
  17. Junio C HamanoMar 23, 2017
  18. Jonathan NiederMar 23, 2017

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.