On Wed, Feb 20, 2013 at 12:20 PM, Denys Vlasenko
wrote:
> On Mon, Feb 4, 2013 at 12:54 PM, Slava Zanko wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> 31.01.2013 19:27, Oswald Buddenhagen wrote:
>>> the mc devs are rather insistent on their process and often simply
>>> ignore con
On Mon, Feb 4, 2013 at 12:54 PM, Slava Zanko wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> 31.01.2013 19:27, Oswald Buddenhagen wrote:
>
>> the mc devs are rather insistent on their process and often simply
>> ignore contributions on the list, so you may get a better response
>> whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
31.01.2013 19:27, Oswald Buddenhagen wrote:
> the mc devs are rather insistent on their process and often simply
> ignore contributions on the list, so you may get a better response
> when you create trac tickets.
It's is not the only reason, but ye
On Thu, Jan 31, 2013 at 11:38:58AM +0100, Denys Vlasenko wrote:
> Ping...
>
the mc devs are rather insistent on their process and often simply
ignore contributions on the list, so you may get a better response when
you create trac tickets.
___
mc-devel m
Ping...
On Thu, Oct 25, 2012 at 4:45 PM, Denys Vlasenko
wrote:
> When we see an unknown sequence, it is not enough
> to drop already received part - there can be more of it
> coming over e.g. a serial line.
>
> To prevent interpreting it as a random garbage,
> eat and discard all chars that follo
When we see an unknown sequence, it is not enough
to drop already received part - there can be more of it
coming over e.g. a serial line.
To prevent interpreting it as a random garbage,
eat and discard all chars that follow.
Small, but non-zero timeout is needed to reconnect
escape sequence split
