From: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
To: git@vger.kernel.org
Cc: hanwen@google.com, gitster@pobox.com,
"Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Subject: [PATCH v2 0/7] hn/reftable "fixes" for BSD
Date: Sun, 15 Aug 2021 18:15:31 -0700 [thread overview]
Message-ID: <20210816011538.34199-1-carenas@gmail.com> (raw)
In-Reply-To: <20210802190054.58282-1-carenas@gmail.com>
A few issues I noticed while buiding "seen" in some BSD systems.
Patches 1-3 aren't changed from v1, and 4 had the fixes suggested by
Junio[1] added.
Patch 5 affects an EOL NetBSD 7.2 system and therefore might be dropped
but I thought it was safe/generic enough and might become useful in
other old systems as well.
The last 2 patches are a well known recurring issue, that even prompted
a explicit documentation update in cc0c42975a (CodingGuidelines: spell
out post-C89 rules, 2019-07-16).
All these patches are expected to be applied on top of hn/reftable and
hopefully absorved and discarded.
Carlo Marcelo Arenas Belón (7):
fixup! Provide zlib's uncompress2 from compat/zlib-compat.c
reftable: clarify zlib version dependency
openbsd: allow reftable building with zlib 1.2.3
fixup! reftable: add dump utility
fixup! Provide zlib's uncompress2 from compat/zlib-compat.c
fixup! reftable: reftable file level tests
fixup! reftable: (de)serialization for the polymorphic record type
Makefile | 2 +-
compat/zlib-uncompress2.c | 3 +++
config.mak.uname | 1 +
reftable/block.c | 4 +++-
reftable/dump.c | 1 +
reftable/readwrite_test.c | 4 ++--
reftable/record_test.c | 4 +++-
7 files changed, 14 insertions(+), 5 deletions(-)
[1] https://lore.kernel.org/git/xmqq35rpqg27.fsf@gitster.g/
--
2.33.0.rc2.476.g1b09a32a73
next prev parent reply other threads:[~2021-08-16 1:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 19:00 [PATCH 0/3] hn/reftable "fixes" for OpenBSD Carlo Marcelo Arenas Belón
2021-08-02 19:00 ` [PATCH 1/3] fixup! Provide zlib's uncompress2 from compat/zlib-compat.c Carlo Marcelo Arenas Belón
2021-08-02 19:00 ` [PATCH 2/3] reftable: clarify zlib version dependency Carlo Marcelo Arenas Belón
2021-08-02 19:00 ` [PATCH 3/3] openbsd: allow reftable building with zlib 1.2.3 Carlo Marcelo Arenas Belón
2021-08-04 6:44 ` [PATCH 4/3] fixup! reftable: add dump utility Carlo Marcelo Arenas Belón
2021-08-04 17:24 ` Junio C Hamano
2021-08-16 1:15 ` Carlo Marcelo Arenas Belón [this message]
2021-08-16 1:15 ` [PATCH v2 1/7] fixup! Provide zlib's uncompress2 from compat/zlib-compat.c Carlo Marcelo Arenas Belón
2021-08-16 1:15 ` [PATCH v2 2/7] reftable: clarify zlib version dependency Carlo Marcelo Arenas Belón
2021-08-16 1:15 ` [PATCH v2 3/7] openbsd: allow reftable building with zlib 1.2.3 Carlo Marcelo Arenas Belón
2021-08-16 1:15 ` [PATCH v2 4/7] fixup! reftable: add dump utility Carlo Marcelo Arenas Belón
2021-08-16 1:15 ` [PATCH v2 5/7] fixup! Provide zlib's uncompress2 from compat/zlib-compat.c Carlo Marcelo Arenas Belón
2021-08-16 1:15 ` [PATCH v2 6/7] fixup! reftable: reftable file level tests Carlo Marcelo Arenas Belón
2021-08-16 1:15 ` [PATCH v2 7/7] fixup! reftable: (de)serialization for the polymorphic record type Carlo Marcelo Arenas Belón
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=20210816011538.34199-1-carenas@gmail.com \
--to=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hanwen@google.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).