Jim Meyering writes:
> On Tue, Mar 7, 2017 at 8:08 AM, Mathieu Lirzin wrote:
>> Hello Jim,
>>
>> Jim Meyering writes:
>>
>>> On Sun, Mar 5, 2017 at 8:12 AM, Mathieu Lirzin wrote:
I have been using 'readme-release' module and was surprised to discover
that the "README-release" fi
On Tue, Mar 7, 2017 at 8:08 AM, Mathieu Lirzin wrote:
> Hello Jim,
>
> Jim Meyering writes:
>
>> On Sun, Mar 5, 2017 at 8:12 AM, Mathieu Lirzin wrote:
>>>
>>> I have been using 'readme-release' module and was surprised to discover
>>> that the "README-release" file was automatically distributed
Hello Jim,
Jim Meyering writes:
> On Sun, Mar 5, 2017 at 8:12 AM, Mathieu Lirzin wrote:
>>
>> I have been using 'readme-release' module and was surprised to discover
>> that the "README-release" file was automatically distributed without any
>> mention in the "module/readme-release" file.
>>
>>
On 7 March 2017 at 12:19, Reuben Thomas wrote:
> I have read the documentation in gnulib, and also dug out the original
> announcement, coincidentally almost exactly 10 years old:
> http://lists.gnu.org/archive/html/bug-gnulib/2003-03/msg00020.html
>
By the way, I noticed that Alexandre Duret-L
On 22 February 2017 at 13:55, Reuben Thomas wrote:
>
> I attach the latest state of play, which consists simply of updated
> versions of manywarnings.m4 and warnings.m4, in place of the new files I
> had before. (To test them I have simply placed them in a gnulib patch
> directory which is appli
I am trying to use relocatable-lib-lgpl, to make Enchant relocatable.
(Enchant is a spell-checker library wrapper, itself a library, and it needs
to be able to find resources such as dictionaries at run-time, relative to
the library's location. See https://github.com/AbiWord/enchant/ )
I have read
