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

[PATCH 0/1] Fix a recently-introduced compile warning

From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Date
Aug 14, 2018, 11:02 UTC
Message-ID
<pull.18.git.gitgitgadget@gmail.com>

With the relatively frequent breakages of pu recently, I had trouble staying on top of the compile errors/test failures, sorry.

This one exists since Sunday, and it is a compile error only with DEVELOPER=1, which is, however, the recommended way to build in Git for Windows' SDK.

Note: it is based on nd/clone-case-smashing-warning.
Johannes Schindelin (1):
  mark_colliding_entries(): fix incorrect #if...#endif guard
 entry.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
base-commit: f80218bf4e65ccc06cc9173c0ac5a5520d380f36
Published-As: https://github.com/gitgitgadget/git/releases/tags/pr-18%2Fdscho%2Fclone-case-smashing-warning-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-18/dscho/clone-case-smashing-warning-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/18
-- 
gitgitgadget
Next: Johannes Schindelin via GitGitGadget
Message 1 of 3 in “Fix a recently-introduced compile warning”
  1. 0/1 Fix a recently-introduced compile warningJohannes Schindelin via GitGitGadget, Aug 14, 2018
  2. 1/1 mark_colliding_entries(): fix incorrect #if...#endif guardJohannes Schindelin via GitGitGadget, Aug 14, 2018
  3. Junio C HamanoAug 14, 2018

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.