From: Russ Cox <russcox@gmail.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] fossil
Date: Fri, 11 Jun 2004 23:12:50 -0400 [thread overview]
Message-ID: <ee9e417a0406112012251afd8f@mail.gmail.com> (raw)
there's a new fossil on sources that should
fix the leaks people have been encountering.
as i mentioned in the other thread, the
console "check" command should be used
in place of flchk. in particular, to fix your leaks
you can do
fsys main
check fix pdir
(of course, snap -a and wait for the vac first,
just in case.) the pdir is optional, but it is good
for seeing that something is going on.
russ
next reply other threads:[~2004-06-12 3:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 3:12 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-17 16:16 [9fans] Interoperating between 9legacy and 9front Noam Preil
2024-05-18 19:08 ` [9fans] fossil Richard Miller
2009-06-04 9:29 Charles Forsyth
2009-06-04 19:25 ` erik quanstrom
2005-01-03 18:37 Bruce Ellis
2005-01-03 18:51 ` Russ Cox
2005-01-04 17:42 ` Russ Cox
2004-03-20 2:27 David Presotto
2003-04-15 5:26 Andrew
2003-04-15 15:12 ` Russ Cox
2003-04-15 21:00 ` Andrew
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=ee9e417a0406112012251afd8f@mail.gmail.com \
--to=russcox@gmail.com \
--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).