hail-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: [PATCH hail] const-correctness tweaks
Date: Sat, 23 Oct 2010 08:47:05 +0200	[thread overview]
Message-ID: <871v7hjthy.fsf@meyering.net> (raw)
In-Reply-To: <4CC23F2B.3090900@garzik.org> (Jeff Garzik's message of "Fri, 22 Oct 2010 21:49:31 -0400")

Jeff Garzik wrote:
...
>> But even if curl were requiring some suboptimal signature,
>> it would be nice not to impose that on all projects that use hail.
>> Are there older curl headers that do require the const-free signature?
>> If there are and you want to support them, too, let me know -- maybe
>> I can cook up an autoconf test to make things work there, with minimal
>> impact.
>
> Nah, I wouldn't worry about the const signature, it's probably just
> out of date documentation.  If users appear running old OS's or OS
> versions, we can tackle autoconf'ing on a piecemeal basis as needs
> arise.
>
> Committed these patches of yours to hail.git and tabled.git.

Thanks!

      parent reply	other threads:[~2010-10-23  6:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 12:07 [PATCH hail] const-correctness tweaks Jim Meyering
2010-10-07  6:00 ` Jeff Garzik
2010-10-07  6:38   ` Jim Meyering
2010-10-19 22:24 ` Jeff Garzik
2010-10-20  8:00   ` Jim Meyering
2010-10-20  8:36     ` Jeff Garzik
2010-10-20  8:53       ` Jim Meyering
2010-10-23  1:49         ` Jeff Garzik
2010-10-23  3:01           ` Jeff Garzik
2010-10-23  6:47           ` Jim Meyering [this message]

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=871v7hjthy.fsf@meyering.net \
    --to=jim@meyering.net \
    --cc=hail-devel@vger.kernel.org \
    --cc=jeff@garzik.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 read-only IMAP folder(s) and NNTP newsgroup(s).