[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mysterious c0 80
From: |
Ralph Corderoy |
Subject: |
Re: mysterious c0 80 |
Date: |
Thu, 04 Jan 2024 14:04:45 +0000 |
Hi Ken,
> It would be nice to understand the root cause of the bug, though.
Yes.
> So while I agree post would fail with this hypothetical dist(1) of a
> message containing a NUL, it's not clear you could inc(1) such a
> message in the first place.
Today or historically? Historically is a long time.
--
Cheers, Ralph.
- Re: mysterious c0 80, (continued)
- Re: mysterious c0 80, Michael Richardson, 2024/01/01
- Re: mysterious c0 80, Ken Hornstein, 2024/01/02
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/02
- Re: mysterious c0 80, Michael Richardson, 2024/01/02
- Re: mysterious c0 80, Ken Hornstein, 2024/01/02
- Re: mysterious c0 80, Michael Richardson, 2024/01/02
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/03
- Re: mysterious c0 80, David Levine, 2024/01/03
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/04
- Re: mysterious c0 80, Ken Hornstein, 2024/01/04
- Re: mysterious c0 80,
Ralph Corderoy <=
- Re: mysterious c0 80, Ken Hornstein, 2024/01/04
- Re: mysterious c0 80, Michael Richardson, 2024/01/04
- Re: mysterious c0 80, David Levine, 2024/01/04
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/05
- Re: mysterious c0 80, Michael Richardson, 2024/01/02
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/02
Re: mysterious c0 80, Michael Richardson, 2024/01/01
Re: mysterious c0 80, Michael Richardson, 2024/01/01