linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Larry McVoy <lm@bitmover.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH *] new struct page shrinkage
Date: Tue, 19 Feb 2002 16:35:26 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.33L.0202191634290.7820-100000@imladris.surriel.com> (raw)
In-Reply-To: <20020219113217.P26350@work.bitmover.com>

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'd suggest a changeset to the config file which says
>
> # Don't change the description unless you are Linus.

Nice warning ;)

regards,

Rik
-- 
"Linux holds advantages over the single-vendor commercial OS"
    -- Microsoft's "Competing with Linux" document

http://www.surriel.com/		http://distro.conectiva.com/

--
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/

  reply	other threads:[~2002-02-19 19:35 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 [this message]
2002-02-19 19:54       ` Larry McVoy
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=Pine.LNX.4.33L.0202191634290.7820-100000@imladris.surriel.com \
    --to=riel@conectiva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lm@bitmover.com \
    --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