On Fri, Sep 22, 2023 at 06:57:24AM +0200, Walter Alejandro Iglesias wrote:
> Below, a version without utf8 parser. I added a ASCII check for the
> subject. The day will come when wscons support UTF-8, right? In the
> meantime, just by being careful not to type iso-latin characters while
> using
Hi Ingo,
On Thu, Sep 21, 2023 at 03:04:24PM +0200, Ingo Schwarze wrote:
> As Stefan says, adding a hand-written UTF-8 parser to mail(1) is
> clearly not acceptable.
Below, a version without utf8 parser. I added a ASCII check for the
subject. The day will come when wscons support UTF-8, right?
A leak may happens when wgpeer is deleted.
ok?
The state queue should be freeed when wg_peer is destroyed.
diff from IIJ.
Index: sys/net/if_wg.c
===
RCS file: /disk/cvs/openbsd/src/sys/net/if_wg.c,v
retrieving revision 1.29
diff -u
In comparison to MI boot which only cares about /bsd.upgrade's x bit,
powerpc64 rdboot just wants a regular file.
Require and strip u+x before execution to prevent sysupgrade(8) loop.
I'm new to powerpc64 and can't think of a reason to be different.
Feedback? Objection? OK?
Regular boot and sysu
On Thu, Sep 21, 2023 at 02:12:50PM +0200, Stefan Sperling wrote:
> On Thu, Sep 21, 2023 at 01:25:01PM +0200, Walter Alejandro Iglesias wrote:
> > I corrected many of the things you pointed me, but not all. The
> > function I use to check utf8 is mine, I use it in a pair of little
> > programs whic
Hi,
i fear this is getting a bit out of hand...
Stefan Sperling wrote on Thu, Sep 21, 2023 at 02:12:50PM +0200:
> On Thu, Sep 21, 2023 at 01:25:01PM +0200, Walter Alejandro Iglesias wrote:
>> I corrected many of the things you pointed me, but not all. The
>> function I use to check utf8 is mine
On Thu, Sep 21, 2023 at 01:25:01PM +0200, Walter Alejandro Iglesias wrote:
> I corrected many of the things you pointed me, but not all. The
> function I use to check utf8 is mine, I use it in a pair of little
> programs which I've *hardly* checked for memory leacks. I know my
> function looks BI
On Thu, Sep 21, 2023 at 11:26:11AM +0200, Omar Polo wrote:
> On 2023/09/21 10:55:47 +0200, Walter Alejandro Iglesias
> wrote:
> > On Wed, Sep 20, 2023 at 08:36:23PM +0200, Walter Alejandro Iglesias wrote:
> > > On Wed, Sep 20, 2023 at 07:44:12PM +0200, Walter Alejandro Iglesias wrote:
> > > > And
On Thu, Sep 21, 2023 at 11:26:11AM +0200, Omar Polo wrote:
> Do we really need the two checks?
WFIW, my original suggestion made off-list was about checking for 0xfe and
0xff only:
Crystal wrote:
> 0xfe and 0xff are invalid in utf-8.
>
> It _might_ be worth detecting them and in this case not ou
On 2023/09/21 10:55:47 +0200, Walter Alejandro Iglesias
wrote:
> On Wed, Sep 20, 2023 at 08:36:23PM +0200, Walter Alejandro Iglesias wrote:
> > On Wed, Sep 20, 2023 at 07:44:12PM +0200, Walter Alejandro Iglesias wrote:
> > > And this new idea simplifies all to this:
> >
> > In case anyone else i
On Wed, Sep 20, 2023 at 08:36:23PM +0200, Walter Alejandro Iglesias wrote:
> On Wed, Sep 20, 2023 at 07:44:12PM +0200, Walter Alejandro Iglesias wrote:
> > And this new idea simplifies all to this:
>
> In case anyone else is worried. Crystal Kolipe already pointed me out
> that a better UTF-8 che
11 matches
Mail list logo
