From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jim Meyering <jim@meyering.net>
Subject: Re: [PATCH hail] const-correctness tweaks
Date: Sat, 23 Oct 2010 08:47:05 +0200
Message-ID: <871v7hjthy.fsf@meyering.net>
References: <87mxqro78a.fsf@meyering.net> <4CBE1AA2.5020004@garzik.org>
	<878w1t5m5k.fsf@meyering.net> <4CBEAA1D.2030302@garzik.org>
	<8739s15jos.fsf@meyering.net> <4CC23F2B.3090900@garzik.org>
Mime-Version: 1.0
Return-path: <hail-devel-owner@vger.kernel.org>
In-Reply-To: <4CC23F2B.3090900@garzik.org> (Jeff Garzik's message of "Fri, 22
	Oct 2010 21:49:31 -0400")
Sender: hail-devel-owner@vger.kernel.org
List-ID: <hail-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail <hail-devel@vger.kernel.org>

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!