From: Jonathan Larmour <jlarmour@redhat.com>
To: yyl <ylyuan@davform.com>
Cc: eCos_discuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] about ram file system and memory management on the cvs
Date: Mon, 30 Oct 2000 07:09:00 -0000 [thread overview]
Message-ID: <39FD8F1F.F12110F6@redhat.com> (raw)
In-Reply-To: <005401c0424f$907b1950$8664a8c0@yyl_nt>
> yyl wrote:
>
> Hi,I want to use ram file system from cvs,but I don't know whether the
> ram file system depends on the
> memory management of cvs?
It depends on malloc(), but no specific implementation of it.
But I think you'd have a hard job disentangling the file system support
from the rest of the CVS world, if that's what you intend to do.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-10-30 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 1:01 yyl
2000-10-30 7:09 ` Jonathan Larmour [this message]
[not found] <005801c042d9$f1d10e00$8664a8c0@yyl_nt>
2000-11-01 7:26 ` Jonathan Larmour
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=39FD8F1F.F12110F6@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=ylyuan@davform.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).