From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: GIT Mailing-list <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Erik Faye-Lund <kusmabite@gmail.com>
Subject: [PATCH 0/3] cygwin-tests patches
Date: Thu, 16 Jun 2011 21:20:59 +0100 [thread overview]
Message-ID: <4DFA65AB.7050605@ramsay1.demon.co.uk> (raw)
Hi Junio,
These patches, from my cygwin-tests branch, fix test failures on
cygwin. I have sent the first two patches to the list before
(patches #8-9/14 of the "misc test-suite patches" series on
14-12-2010), but they didn't even make it to the pu branch!
[You requested help in reviewing them.]
The final patch corresponds to the RFC patch sent late last week
(9-6-2011) which has an updated commit message, but is otherwise
unchanged.
[PATCH 1/3] help.c: Fix detection of custom merge strategy on cygwin
[PATCH 2/3] t1301-*.sh: Fix the 'forced modes' test on cygwin
[PATCH 3/3] config.c: Make git_config() work correctly when called recursively
Ah, ... I just noticed that the original RFC patch is already in
pu, merged from rj/config-cygwin. Hmm, do you want to split that
off from this series again?
ATB,
Ramsay Jones
reply other threads:[~2011-06-16 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DFA65AB.7050605@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@gmail.com \
--cc=peff@peff.net \
/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).