From: igor@9lab.org
To: 9front@9front.org
Subject: Re: [9front] Howto: debugging with acid(1)
Date: Fri, 15 Oct 2021 13:45:41 +0200 [thread overview]
Message-ID: <C527C3E1513672BD7A1171BE55E99178@9lab.org> (raw)
In-Reply-To: <3E7DDC73061E987C79BF3D692D357C51@wopr.sciops.net>
Hi qwx,
Quoth qwx@sciops.net:
> On Wed Oct 13 17:19:36 +0200 2021, igor@9lab.org wrote:
> > Finally I organised my scattered notes on debugging with acid(1)
> > and put it together into a howto with screencast:
> >
> > * https://9lab.org/plan9/debugging-with-acid/
[…]
> Thank you for this document, it's a useful writeup. Please
> consider also adding it to or mirroring it on the wiki[1], where
> others could put more tips as well.
[…]
Will do. The Wiki is indeed a very useful place ☺ and I believe
I do have access.
Cheers,
Igor
next prev parent reply other threads:[~2021-10-15 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 15:11 igor
2021-10-13 22:32 ` David Leimbach
2021-10-14 19:34 ` qwx
2021-10-15 11:45 ` igor [this message]
2021-10-15 14:06 ` Stuart Morrow
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=C527C3E1513672BD7A1171BE55E99178@9lab.org \
--to=igor@9lab.org \
--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).