From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
From: nemo@plan9.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] big pull
Date: Thu, 26 Jun 2003 10:10:28 +0200 [thread overview]
Message-ID: <3ec3b42a43aea90a3b142db0014cb1f7@plan9.escet.urjc.es> (raw)
In-Reply-To: <050b40a7e24813021540a00585ab200f@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
As I said in a previous mail, I think there's actually no real problem.
After a few days fossil does not grow more than other programs.
I'm sorry if I didnt make it clear before.
[-- Attachment #2: Type: message/rfc822, Size: 1585 bytes --]
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] big pull
Date: Wed, 25 Jun 2003 21:59:47 -0400
Message-ID: <050b40a7e24813021540a00585ab200f@plan9.bell-labs.com>
> By the way, the problem reported by Nemo before of fossil's
> memory leak has been fixed in the big pull? Or the problem
> was not recognized?
Reproduce it and run leak, please. Until then,
there's little we can do.
Russ
prev parent reply other threads:[~2003-06-26 8:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 10:35 Russ Cox
2003-06-23 10:49 ` Lucio De Re
2003-06-23 10:56 ` Lucio De Re
2003-06-24 2:20 ` Russ Cox
2003-06-23 14:02 ` Joel Salomon
2003-06-23 14:03 ` boyd, rounin
2003-06-23 14:20 ` Joel Salomon
2003-06-24 2:18 ` Russ Cox
2003-06-24 3:05 ` okamoto
2003-06-25 0:26 ` Russ Cox
2003-06-25 2:38 ` okamoto
2003-06-25 7:48 ` Fco.J.Ballesteros, nemo
2003-06-25 7:50 ` Lucio De Re
2003-06-25 8:01 ` Fco.J.Ballesteros, nemo
2003-06-25 7:56 ` Lucio De Re
2003-06-25 9:25 ` Richard Miller, miller
2003-06-26 1:57 ` Russ Cox
2003-06-26 9:11 ` Richard Miller, miller
2003-06-26 1:59 ` Russ Cox
2003-06-26 8:10 ` Fco.J.Ballesteros, nemo [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=3ec3b42a43aea90a3b142db0014cb1f7@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).