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

Re: [PATCH 14/14] wt-status.c: Initialise variable to suppress msvc warning

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 9, 2010, 19:08 UTC
Message-ID
<7vmxoeg3wp.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4D011D30.4070405@ramsay1.demon.co.uk>
Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:
> Junio, could you please drop patches 5-14 from the series; the first four patches
> are the important ones and I'd rather they didn't get held up. Thanks!
Have these four patches been Acked by interested parties?

I think I saw 1/N and 2/N acked by Erik and 4/N acked by SSchuberth and J6t, but any words on 3/N?

Not that I deeply care nor have environment to test changes to [3/N], but I am wondering if these need conditional definition to futureproof (e.g. what happens when the header you are using the definition _I64_MIN from, or some other headers, started defining these constats?).

Previous: Ramsay JonesNext: Erik Faye-Lund
Message 4 of 8 in “wt-status.c: Initialise variable to suppress msvc warning”
  1. 14/14 wt-status.c: Initialise variable to suppress msvc warningRamsay Jones, Dec 4, 2010
  2. Jonathan NiederDec 4, 2010
  3. Ramsay JonesDec 9, 2010
  4. Junio C HamanoDec 9, 2010
  5. Erik Faye-LundDec 9, 2010
  6. Sebastian SchuberthDec 10, 2010
  7. Erik Faye-LundDec 10, 2010
  8. Sebastian SchuberthDec 10, 2010

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.