> On 11 Oct 2017, at 11:38 am, Warren Young wrote:
>
> [snip]
> By the way, there seem to be a lot of changes upstream to Autosetup which
> haven’t been pulled in yet. Time for an autosetup --install?
I've updated autosetup and pushed the changes to branch autosetup
Cheers,
Steve
> On 12 May 2017, at 2:30 PM, Steve Bennett wrote:
>
> On 12 May 2017, at 2:12 PM, Steve Bennett wrote:
>>
>> On 12 May 2017, at 9:39 AM, Joe Mistachkin wrote:
>>>
>>>
>>> Ross Berteig wrote:
>>>>
>>>> I've been
On 12 May 2017, at 2:12 PM, Steve Bennett wrote:
>
> On 12 May 2017, at 9:39 AM, Joe Mistachkin wrote:
>>
>>
>> Ross Berteig wrote:
>>>
>>> I've been trying to chase down a minimal patch to autosetup to make our
>>> configure
On 12 May 2017, at 9:39 AM, Joe Mistachkin wrote:
>
>
> Ross Berteig wrote:
>>
>> I've been trying to chase down a minimal patch to autosetup to make our
>> configure work again. This was reported on fossil-users early this
>> morning, and I can confirm that my build and test automation here
On 21 Sep 2016, at 2:44 AM, Joe Mistachkin wrote:
>
>
> Please review the changes on the "autosetupAndJimTcl" branch, which
> updates the included autosetup and Jim with the latest code from
> upstream.
>
> Since both of these projects are maintained by Steve
> On 12 Jun 2015, at 5:23 am, Richard Hipp wrote:
>
> On 6/11/15, Stephan Beal wrote:
>>
>>> "A" - in other words swap the CapsLock and Ctrl keys - otherwise your
>>> pinky is a goner.
>>>
>>
>>
>> That's a great idea. i'll take a look at that (will help with bash, in any
>> case).
>>
>
>
