From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: [PATCH 0/3] misc patches on next branch
Date: Sun, 11 Sep 2011 20:37:49 +0100 [thread overview]
Message-ID: <4E6D0E0D.2000400@ramsay1.demon.co.uk> (raw)
Hi Junio,
These patches are built on the next branch (from repo.or.cz)
@ 12850bec0c24b529c9a9df6a95ad4bdeea39373e
[PATCH 1/3] sparse: Fix some "symbol not declared" warnings
[PATCH 2/3] Fix some "variable might be used uninitialized" warnings
[PATCH 3/3] Makefile: Make dependency directory creation less noisy
Note that the next branch does not build on MinGW at the moment due
to the credentials-cache[--daemon] additions; rather the use of unix
sockets to be more precise. I had intended to fix this up by now (one
option being to emulate unix sockets with win32 named pipes) but I
haven't had time - sorry!
ATB,
Ramsay Jones
reply other threads:[~2011-09-11 19:44 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=4E6D0E0D.2000400@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).