public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Roland Bless <bless@tm.uka.de>,
	miquels@cistron.nl, linux-kernel@vger.kernel.org,
	walter@tm.uka.de, winter@tm.uka.de, doll@tm.uka.de
Subject: Re: Fix for wrong OOM killer trigger?
Date: Fri, 19 Sep 2003 13:52:20 -0700	[thread overview]
Message-ID: <20030919205220.GA19830@work.bitmover.com> (raw)
In-Reply-To: <20030919200117.GE1312@velociraptor.random>

On Fri, Sep 19, 2003 at 10:01:17PM +0200, Andrea Arcangeli wrote:
> Andrea - If you refuse to depend on closed software for a critical
> 	 part of your business, these links may be useful:
> 	  rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/
> 	  http://www.cobite.com/cvsps/
> 	  svn://svn.kernel.org/linux-2.[46]/trunk
> -------------------------
> 
> Hope it's ok in terms of bandwidth now.
> 
> And if you don't like the text I write in my signature, I'm sorry and I
> would simply suggest you to not read it. If you need a marker to cleanup
> it reliably just ask me and I'll be glad to add it. IMHO the value those
> services provides is too high not to advertize them as much as I
> possibly can.

Then put the URL's in the FAQ and be done with it.  

I can assure you that the first time the CVS gateway has a problem it
won't come back until you have stopped being rude.  You do understand
that the SVN and RSYNC data come from the CVS gateway and that the
CVS gateway comes from BitMover and that all of this crap is hosted by
BitMover, right?  {cvs,svn}.kernel.org are cnames for kernel.bkbits.net.

Here's a suggested replacement signature, it accomplishes your goal of
advertising the services.  Why this needs to be here and not in the FAQ
is beyond me.

/*
 * SCM access to the kernel
 *
 * BitKeeper:	bk://linux.bkbits.net/linux-2.[45]
 * CVS:		:pserver:anonymous@cvs.kernel.org:/home/cvs/linux-2.[45]
 * RSYNC:	rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/
 * Subversion:	svn://svn.kernel.org/linux-2.[46]/trunk
 */
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-09-19 20:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 17:16 Fix for wrong OOM killer trigger? Roland Bless
2003-09-19 17:30 ` Marc-Christian Petersen
2003-09-19 19:25 ` Andrea Arcangeli
2003-09-19 19:35   ` Russell King
2003-09-19 20:01     ` Andrea Arcangeli
2003-09-19 20:52       ` Larry McVoy [this message]
2003-09-19 21:05         ` Formal complaint , " Mr. James W. Laferriere
2003-09-20  6:36           ` David S. Miller
2003-09-20  3:31         ` Andrea Arcangeli
2003-09-20  4:30           ` Larry McVoy
2003-09-20 12:22             ` Bernd Schmidt
2003-09-20 13:52               ` Willy Tarreau
2003-09-20 13:54               ` Larry McVoy
2003-09-20 19:56                 ` Gateways (was Re: Fix for wrong OOM killer trigger?) Jamie Lokier
2003-09-20 20:14                   ` Larry McVoy
2003-09-21 11:52                     ` David S. Miller
2003-09-20 16:07               ` Fix for wrong OOM killer trigger? Valdis.Kletnieks
2003-09-20 14:23             ` Andrea Arcangeli
2003-09-20 15:13               ` Larry McVoy
2003-09-20 17:14                 ` Flames (was: Fix for wrong OOM killer trigger?) Stephen Satchell
2003-09-20 17:46                   ` Alan Cox
2003-09-21 10:40                 ` Fix for wrong OOM killer trigger? Eric W. Biederman
2003-09-21 14:22                   ` Andrea Arcangeli
2003-09-21 14:52                     ` Larry McVoy
2003-09-21 15:53                       ` Andrea Arcangeli
2003-09-23 12:46                     ` Bas Mevissen
2003-09-20 11:09   ` Roland Bless
2003-09-20 14:34     ` Andrea Arcangeli
2003-09-22 10:11       ` Roland Bless
2003-09-22 13:02         ` Andrea Arcangeli

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=20030919205220.GA19830@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=andrea@suse.de \
    --cc=bless@tm.uka.de \
    --cc=doll@tm.uka.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    --cc=walter@tm.uka.de \
    --cc=winter@tm.uka.de \
    /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