git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Prohaska <prohaska@zib.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Johannes Sixt <johannes.sixt@telecom.at>,
	Steffen Prohaska <prohaska@zib.de>
Subject: [PATCH 0/5] A few minor MinGW changes
Date: Sat, 23 May 2009 10:04:46 +0200	[thread overview]
Message-ID: <1243065891-13270-1-git-send-email-prohaska@zib.de> (raw)

Here are a few simple commits that are included in the msysgit
release but not in git.git.

        Steffen

Johannes Schindelin (4):
  MinGW: the path separator to split GITPERLLIB is ';' on Win32
  MinGW: use POSIX signature of waitpid()
  MinGW: Add a simple getpass()
  MinGW: Fix compiler warning in merge-recursive

Peter Harris (1):
  MinGW: Scan for \r in addition to \n when reading shbang lines

 Makefile                  |    4 +++-
 builtin-merge-recursive.c |    5 +++--
 compat/mingw.c            |   19 +++++++++++++++++--
 compat/mingw.h            |    4 +++-
 4 files changed, 26 insertions(+), 6 deletions(-)

             reply	other threads:[~2009-05-23  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23  8:04 Steffen Prohaska [this message]
2009-05-23  8:04 ` [PATCH 1/5] MinGW: Scan for \r in addition to \n when reading shbang lines Steffen Prohaska
2009-05-23  8:04   ` [PATCH 2/5] MinGW: the path separator to split GITPERLLIB is ';' on Win32 Steffen Prohaska
2009-05-23  8:04     ` [PATCH 3/5] MinGW: use POSIX signature of waitpid() Steffen Prohaska
2009-05-23  8:04       ` [PATCH 4/5] MinGW: Add a simple getpass() Steffen Prohaska
2009-05-23  8:04         ` [PATCH 5/5] MinGW: Fix compiler warning in merge-recursive Steffen Prohaska

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=1243065891-13270-1-git-send-email-prohaska@zib.de \
    --to=prohaska@zib.de \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.sixt@telecom.at \
    /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).