git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git Mailing List <git@vger.kernel.org>,
	msysGit <msysgit@googlegroups.com>
Subject: Re: MinGW port pull request
Date: Sat, 21 Jun 2008 02:46:36 -0700	[thread overview]
Message-ID: <7vskv79l37.fsf@gitster.siamese.dyndns.org> (raw)
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.

  reply	other threads:[~2008-06-21  9:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20  8:06 MinGW port pull request Johannes Sixt
2008-06-21  9:46 ` Junio C Hamano [this message]
2008-06-21 21:18   ` [msysGit] " Johannes Sixt
2008-06-21 21:21     ` Jim Raden
2008-06-21 21:47     ` [msysGit] " Junio C Hamano
2008-06-23 11:54     ` Johannes Sixt
2008-06-24 13:01   ` Johannes Sixt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vskv79l37.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=msysgit@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).