From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Jeff King <peff@peff.net>
Cc: "Vicent Marti" <tanoku@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Torsten Bögershausen" <tboegi@web.de>,
"GIT Mailing-list" <git@vger.kernel.org>
Subject: [PATCH 0/5] fix up 'jk/pack-bitmap' branch
Date: Thu, 07 Nov 2013 21:58:02 +0000 [thread overview]
Message-ID: <527C0CEA.4020705@ramsay1.demon.co.uk> (raw)
Hi Jeff,
These patches fix various errors/warnings on the cygwin, MinGW and
msvc builds, provoked by the jk/pack-bitmap branch.
Note that this does not fix all problems on the msvc build; I have
a solution, but I don't like it. :-D So, I'm going to try a different
fix. I had hoped to have done this by now, but ... (hopefully, sometime
this weekend).
Note that I have only tested the cygwin and MinGW builds by running
the t5310-pack-bitmaps.sh test, and only on a little-endian machine.
(Torsten has tested the first patch on a big-endian)
Note also, that these patches are build on top of the 'pu' branch
as of yesterday (pu @ 2b65d9ebc).
So, could you please squash these patches into the relevant commits
on your branch.
Thanks!
ATB,
Ramsay Jones
Ramsay Jones (5):
compat/bswap.h: Fix build on cygwin, MinGW and msvc
Makefile: Add object files in ewah/ to clean target
khash.h: Spell the null pointer as NULL
pack-objects: Limit visibility of 'indexed_commits' symbols
ewah_bitmap.c: Fix printf format warnings on MinGW
Makefile | 5 +--
builtin/pack-objects.c | 6 ++--
compat/bswap.h | 97 +++++++++++++++++++++++++++++++++++---------------
ewah/ewah_bitmap.c | 6 ++--
khash.h | 2 +-
5 files changed, 79 insertions(+), 37 deletions(-)
--
1.8.4
next reply other threads:[~2013-11-07 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 21:58 Ramsay Jones [this message]
2013-11-07 22:19 ` [PATCH 0/5] fix up 'jk/pack-bitmap' branch Jeff King
2013-11-08 1:39 ` Vicent Martí
2013-11-08 17:10 ` Torsten Bögershausen
2013-11-08 18:23 ` Ramsay Jones
2013-11-08 22:29 ` Jeff King
2013-11-09 11:35 ` Torsten Bögershausen
2013-11-09 17:25 ` Johannes Sixt
2013-11-09 21:03 ` Thomas Rast
2013-11-09 21:21 ` Jeff King
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=527C0CEA.4020705@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=tanoku@gmail.com \
--cc=tboegi@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.