Re: octave mailing lists
Nicholas Jankowski <[email protected]> Thu, 16 Feb 2023 12:46:38 -0500
| Newsgroups | gmane.comp.gnu.octave.general,gmane.comp.gnu.octave.maintainers |
|---|---|
| Message-ID | <CALW4+bKOrw54rDJP21zKEmYNZWhNERV2rdSnXPw6xfFqrhTxNA@mail.gmail.com> |
--===============7186251300658929611== Content-Type: multipart/alternative; boundary="000000000000f4e79a05f4d4c8d7" --000000000000f4e79a05f4d4c8d7 Content-Type: text/plain; charset="UTF-8" > > octave.discourse is FUBAR again. > Looking now, it seems ok. What issues are you seeing? --000000000000f4e79a05f4d4c8d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex"><div dir=3D"ltr"><div style=3D"font-family:monospace;fon= t-size:large">octave.discourse is FUBAR again.=C2=A0</div></div></blockquot= e><div><br></div><div>=C2=A0Looking now, it seems ok. What issues are you s= eeing?</div></div></div> --000000000000f4e79a05f4d4c8d7-- --===============7186251300658929611== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline Ci0tLS0tLS0tLS0KV2UgYXJlIHRyYW5zaXRpb25pbmcgdG8gYSB3ZWIgYmFzZWQgZm9ydW0KZm9y IGNvbW11bml0eSBoZWxwIGRpc2N1c3Npb25zIGF0Cmh0dHBzOi8vb2N0YXZlLmRpc2NvdXJzZS5n cm91cC9jL2hlbHAK --===============7186251300658929611==--