From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] debug prints leaking int sources (sam(1))
Date: Wed, 23 Oct 2013 21:47:30 +0100 [thread overview]
Message-ID: <027bddb81de43ee9005395f690249b59@quintile.net> (raw)
there seem to be some debug prints in the source of sam on sources,
some of which are not actually pushed (in replica's database) yet,
yet others are.
term; sam
fixname: /sys/src/cmd/sam/~~sam~~
fixname: /sys/src/cmd/sam/~~sam~~
getfile: /sys/src/cmd/sam/plan9.c
loadflist: /sys/src/cmd/sam/plan9.c
loadflist: /sys/src/cmd/sam/plan9.c
fixname: /sys/src/cmd/sam/plan9.c
fixname: /sys/src/cmd/sam/plan9.c
-Steve
reply other threads:[~2013-10-23 20:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=027bddb81de43ee9005395f690249b59@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).