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

Re: MinGW port pull request

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 21, 2008, 09:46 UTC
Message-ID
<7vskv79l37.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<485B6510.3080201@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
> please pull the MinGW (Windows) port patch series from
>
> git://repo.or.cz/git/mingw/j6t.git for-junio
Took a look.  A quick impression.
 * Too many whitespace breakages in borrowed compat/regex.[ch] are very
   distracting.
 * It is a very nice touch to rename sample templates to make sure they
   are not executable (after all they are just samples).
 * Shouldn't my_mktime() if exported out of date.c be named a bit better?
 * The ifdef block in git.c::main() introduces decl-after-stmt which we
   tend to avoid, but it is much worse to solve it by adding another ifdef
   block just to enclose decl of char *bslash at the beginning of the
   function.  Perhaps enclose it in an extra block?
 * In sanitary_path_copy(), you left "break;" after /* (1) */ but now that
   "break" is not inside a switch() anymore, so you are breaking out of
   something else, aren't you?  -- Ah, the clean-up phase will be no-op in
   that case because src points at '\0'.  Tricky but looks correct ;-)
 * There seem to be an unrelated general fix in upload-pack.c
 * There are still too many ifdefs.  I am wondering if the changes to
   pager and process stuff is easier to manage in the longer term if they
   are made into completely separate files (i.e. instead of linking
   pager.o you would link mingw-pager.o).  I dunno.
 * There is an interaction with dr/ceiling topic that is already in 'next'
   that needs to be resolved before we merge this in 'next'.
Parked in 'pu' for now but with a broken merge resolution.
Previous: Johannes SixtNext: Johannes Sixt
Message 2 of 7 in “MinGW port pull request”
  1. Johannes SixtJun 20, 2008
  2. Junio C HamanoJun 21, 2008
  3. Johannes SixtJun 21, 2008
  4. Jim RadenJun 21, 2008
  5. Junio C HamanoJun 21, 2008
  6. Johannes SixtJun 23, 2008
  7. Johannes SixtJun 24, 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.