From: Reuben Hawkins <reubenhwk@gmail.com>
To: git@vger.kernel.org
Subject: v2 patches for fixes on RHEL3
Date: Wed, 7 Jan 2015 12:23:53 -0800 [thread overview]
Message-ID: <1420662236-27593-1-git-send-email-reubenhwk@gmail.com> (raw)
In-Reply-To: <CAPig+cSFAzsUj2sOaCyPTu_U8_c5qkF1qQo4nzecVzY0TqmJpg@mail.gmail.com>
These patches add a few autoconfig checks for nanosecond resolution fields in
struct stat, CLOCK_MONOTONIC, and HMAC_CTX_cleanup. I'm fairly sure I've fixed
the concerns/doubts the first set of patched raised.
(I rarely use git-send-email so forgive me if I botch this)
next prev parent reply other threads:[~2015-01-07 20:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 18:53 [PATCH 1/3] configure.ac: check tv_nsec field in struct stat Reuben Hawkins
2014-12-21 18:53 ` [PATCH 2/3] configure.ac,trace.c: check for CLOCK_MONOTONIC Reuben Hawkins
2014-12-21 20:54 ` Eric Sunshine
2014-12-22 4:12 ` brian m. carlson
2014-12-22 12:36 ` Reuben Hawkins
2014-12-21 18:53 ` [PATCH 3/3] configure.ac,imap-send.c: check HMAC_CTX_cleanup Reuben Hawkins
2014-12-21 21:28 ` Eric Sunshine
2015-01-07 20:23 ` Reuben Hawkins [this message]
2015-01-07 20:23 ` [PATCH 1/3] configure.ac: check tv_nsec field in struct stat Reuben Hawkins
2015-01-07 21:19 ` Eric Sunshine
2015-01-07 21:33 ` Reuben Hawkins
2015-01-07 21:57 ` Eric Sunshine
2015-01-07 22:19 ` Reuben Hawkins
2015-01-08 5:41 ` Eric Sunshine
2015-01-07 20:23 ` [PATCH 2/3] configure.ac: check for clock_gettime and CLOCK_MONOTONIC Reuben Hawkins
2015-01-07 21:37 ` Eric Sunshine
2015-01-07 22:31 ` Reuben Hawkins
2015-01-08 5:54 ` Eric Sunshine
2015-01-07 20:23 ` [PATCH 3/3] configure.ac: check for HMAC_CTX_cleanup Reuben Hawkins
2015-01-07 21:46 ` Eric Sunshine
2014-12-21 20:20 ` [PATCH 1/3] configure.ac: check tv_nsec field in struct stat Eric Sunshine
2014-12-21 21:47 ` Eric Sunshine
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=1420662236-27593-1-git-send-email-reubenhwk@gmail.com \
--to=reubenhwk@gmail.com \
--cc=git@vger.kernel.org \
/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).