From: Eric Sandeen <sandeen@sandeen.net>
To: eric c <xcellula@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Is CVS stable?
Date: Wed, 20 Feb 2008 08:13:12 -0600 [thread overview]
Message-ID: <47BC3578.5050209@sandeen.net> (raw)
In-Reply-To: <eb736a810802200026g1b956abar922548d3e67a9682@mail.gmail.com>
eric c wrote:
> Hello,
>
> I have recently seen some patches for slabcache related
> xfs_inode/xfs_vnode_t/dentry_cache taking up alot of memory:
> http://oss.sgi.com/archives/xfs/2007-12/msg00154.html
> http://oss.sgi.com/archives/xfs/2008-02/msg00138.html
>
> If I cvs on linux-2.6-xfs, is it stable for production or bleeding?
I'd never consider any cvs head as "stable for production"
That said, the xfs cvs tree is probably one of the more stable
bleeding-edge trees you'll find. ;)
-Eric
> Thanks
> eric c
> xcellula@gmail.com
>
>
next prev parent reply other threads:[~2008-02-20 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 8:26 Is CVS stable? eric c
2008-02-20 8:45 ` Klaus Strebel
2008-02-20 14:13 ` Eric Sandeen [this message]
2008-02-20 21:21 ` David Chinner
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=47BC3578.5050209@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xcellula@gmail.com \
--cc=xfs@oss.sgi.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