Hi Joe,
On 11 July 2018 at 13:32, Joe Hershberger wrote:
> On Tue, Jul 10, 2018 at 3:49 PM, Simon Glass wrote:
>> Hi Joe,
>>
>> On 9 July 2018 at 13:26, Joe Hershberger wrote:
>>> On Sun, Jul 8, 2018 at 9:39 PM, Simon Glass wrote:
Hi Joe,
On 2 July 2018 at 18:06, Joe Hershberger
On Tue, Jul 10, 2018 at 3:49 PM, Simon Glass wrote:
> Hi Joe,
>
> On 9 July 2018 at 13:26, Joe Hershberger wrote:
>> On Sun, Jul 8, 2018 at 9:39 PM, Simon Glass wrote:
>>> Hi Joe,
>>>
>>> On 2 July 2018 at 18:06, Joe Hershberger wrote:
In raw mode, handle ctrl-c as normal. This allows norm
Hi Joe,
On 9 July 2018 at 13:26, Joe Hershberger wrote:
> On Sun, Jul 8, 2018 at 9:39 PM, Simon Glass wrote:
>> Hi Joe,
>>
>> On 2 July 2018 at 18:06, Joe Hershberger wrote:
>>> In raw mode, handle ctrl-c as normal. This allows normal ctrl-c behavior
>>> such as aborting a command that is timin
On Sun, Jul 8, 2018 at 9:39 PM, Simon Glass wrote:
> Hi Joe,
>
> On 2 July 2018 at 18:06, Joe Hershberger wrote:
>> In raw mode, handle ctrl-c as normal. This allows normal ctrl-c behavior
>> such as aborting a command that is timing out without completely
>> terminating the sandbox executable.
>
Hi Joe,
On 2 July 2018 at 18:06, Joe Hershberger wrote:
> In raw mode, handle ctrl-c as normal. This allows normal ctrl-c behavior
> such as aborting a command that is timing out without completely
> terminating the sandbox executable.
>
> In [1], Simon disabled this. His reason for it was that
In raw mode, handle ctrl-c as normal. This allows normal ctrl-c behavior
such as aborting a command that is timing out without completely
terminating the sandbox executable.
In [1], Simon disabled this. His reason for it was that it interferes
with piping test scripts. Piping should be done in co
6 matches
Mail list logo