From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SYSR1?
Date: Sat, 19 Mar 2005 19:20:00 +0000 [thread overview]
Message-ID: <8a11c1f7653ad2a0665c7f0ee9c0a524@terzarima.net> (raw)
In-Reply-To: <Pine.BSI.4.61.0503190858110.25349@malasada.lava.net>
it was once the part that's commented out:
print("[%s %s %lud] r1 = %lud\n", up->user, up->text, up->pid, arg[0]);
and was sometimes invoked in initcode for initial debugging.
i think i used it once or twice.
now it seems to be used for debugging random things.
incref/decref most recently, i'd guess.
prev parent reply other threads:[~2005-03-19 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 18:59 Tim Newsham
2005-03-19 19:20 ` Charles Forsyth [this message]
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=8a11c1f7653ad2a0665c7f0ee9c0a524@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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).