From: Blue-Maned_Hawk <bluemanedhawk@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Libaml does not recognize opcode 0x86
Date: Mon, 23 Oct 2023 23:00:33 -0400 [thread overview]
Message-ID: <e894585d-540a-4078-b0fc-fbc98ab0fefb@invalid.invalid> (raw)
In-Reply-To: <ZTcuCeLqAxbIw0x4@wopr>
On 10/23/23 22:38, Kurt H Maier wrote:
> On Mon, Oct 23, 2023 at 09:18:52PM -0400, Blue-Maned_Hawk wrote:
>> I made no insistence that it “should be obvious”. Contrary to your claim of
>> loweffortness, I _did_ make an effort, that being to include only the needed
>> information.
>
> You forgot to include any information supporting the implicit assumption
> that people on this mailing list should give a shit that libaml does not
> recognize opcode 0x86.
Okay: it prevents batteries from being recognized as existing. Works
that for you?
> You have still failed to include any information
> which would enable someone, in the event they unilaterally decided to
> give a shit anyway, to do anything useful with the information you have
> so inexpertly provided.
I seen't what info'd be necessary. Please clarify.
> In other words, you are not qualified to ascertain what information is
> needed, and you did it wrong. For this, and many other reasons, I am
> glad you can't get a battery readout on your (likely stolen) computer.
That accusation of theft seems to me completely out of left field.
Where on earth did you get it from?
next prev parent reply other threads:[~2023-10-24 3:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 21:05 Blue-Maned_Hawk
2023-10-23 21:14 ` Jacob Moody
2023-10-23 21:48 ` Blue-Maned_Hawk
2023-10-23 22:04 ` B. Atticus Grobe
2023-10-23 23:21 ` Blue-Maned_Hawk
2023-10-23 23:54 ` ori
2023-10-24 0:12 ` Blue-Maned_Hawk
2023-10-24 0:52 ` ori
2023-10-24 0:53 ` Kurt H Maier
2023-10-23 22:22 ` ori
2023-10-24 0:38 ` Kurt H Maier
2023-10-24 0:57 ` Blue-Maned_Hawk
2023-10-24 1:07 ` Michael Misch
2023-10-24 1:18 ` Blue-Maned_Hawk
2023-10-24 2:38 ` Kurt H Maier
2023-10-24 3:00 ` Blue-Maned_Hawk [this message]
2023-10-24 3:18 ` Kurt H Maier
2023-10-24 3:26 ` Ellenor Bjornsdottir
2023-10-24 3:32 ` Kurt H Maier
2023-10-24 3:32 ` Blue-Maned_Hawk
2023-10-24 3:37 ` Kurt H Maier
2023-10-24 3:52 ` Blue-Maned_Hawk
2023-10-24 4:03 ` unobe
2023-10-24 5:46 ` Lucas Francesco
2023-10-24 3:16 ` Ellenor Bjornsdottir
2023-10-24 3:23 ` Kurt H Maier
2023-10-24 3:35 ` Blue-Maned_Hawk
2023-10-24 3:43 ` B. Atticus Grobe
2023-10-24 3:53 ` Blue-Maned_Hawk
2023-10-24 8:46 ` hiro
2023-10-24 3:55 ` Tonight on Top Gear: ACPI problems, me learning a thing, and accusations of theft (was Re: [9front] Libaml does not recognize opcode 0x86) Ellenor Bjornsdottir
2023-10-24 4:04 ` [9front] multiple sending Ellenor Bjornsdottir
2023-10-24 4:10 ` Tonight on Top Gear: ACPI problems, me learning a thing, and accusations of theft (was Re: [9front] Libaml does not recognize opcode 0x86) Jacob Moody
2023-10-24 3:59 ` Ellenor Bjornsdottir
2023-10-24 4:03 ` [9front] Tonight on Top Gear. ACPI problems, me learning a thing, and accusations of theft Ellenor Bjornsdottir
2023-10-24 5:09 ` Kurt H Maier
2023-10-24 5:29 ` Ellenor Bjornsdottir
2023-10-24 5:43 ` Kurt H Maier
2023-10-24 6:06 ` [9front] Theatre of the absurd Ellenor Bjornsdottir
2023-10-24 6:27 ` Kurt H Maier
2023-10-24 3:57 [9front] Libaml does not recognize opcode 0x86 unobe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e894585d-540a-4078-b0fc-fbc98ab0fefb@invalid.invalid \
--to=bluemanedhawk@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).