From: Larry McVoy <lm@bitmover.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Larry McVoy <lm@bitmover.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Amy Graf <amy@bitmover.com>
Subject: Re: [PATCH *] new struct page shrinkage
Date: Tue, 19 Feb 2002 11:54:52 -0800 [thread overview]
Message-ID: <20020219115452.S26350@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0202191634290.7820-100000@imladris.surriel.com>; from riel@conectiva.com.br on Tue, Feb 19, 2002 at 04:35:26PM -0300
On Tue, Feb 19, 2002 at 04:35:26PM -0300, Rik van Riel wrote:
> On Tue, 19 Feb 2002, Larry McVoy wrote:
> > This is really a problem for bkbits to solve if I understand it
> > correctly. Rik wants to "name" his tree. If we the bkbits admin
> > interface have a "desc" command which changes the description listed
> > on the web pages, then I think he'll be happy, right?
>
> Indeed. The problem was that I was getting too many trees
> on linuxvm.bkbits.net and would only end up confusing people
> what was what...
I've got Amy working on a change so you can do a
admin shell>> desc [-rrepo] whatever you want
and it will change the description to "whatever you want" on repo if specified,
or all if not.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-02-19 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 14:34 Rik van Riel
2002-02-19 16:09 ` Jeff Garzik
2002-02-19 17:30 ` Rik van Riel
2002-02-19 19:21 ` Linus Torvalds
2002-02-19 19:27 ` Rik van Riel
2002-02-19 19:32 ` Larry McVoy
2002-02-19 19:35 ` Rik van Riel
2002-02-19 19:54 ` Larry McVoy [this message]
2002-02-19 19:41 ` Rik van Riel
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=20020219115452.S26350@work.bitmover.com \
--to=lm@bitmover.com \
--cc=amy@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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