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/2] spare warnings on master
Date: Sun, 11 Sep 2011 20:24:18 +0100 [thread overview]
Message-ID: <4E6D0AE2.8040200@ramsay1.demon.co.uk> (raw)
Hi Junio,
These patches fix some sparse warnings on the master branch
(from repo.or.cz) @ 3793ac56b4c4f9bf0bddc306a0cec21118683728
[PATCH 1/2] sparse: Fix an "Using plain integer as NULL pointer"
[PATCH 2/2] obstack.c: Fix some sparse warnings
They could be squashed into one commit, if you prefer. The second
patch is not required on Linux, because *all* of the code in obstack.c
is #ifdef'd out, but it fixes things up on cygwin and MinGW.
ATB,
Ramsay Jones
reply other threads:[~2011-09-11 19:43 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=4E6D0AE2.8040200@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).