linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sanders <linux@sandersweb.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Adrian Bunk <bunk@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Btrfs mainline plans
Date: Wed, 8 Oct 2008 13:48:50 -0400	[thread overview]
Message-ID: <200810081348.50710.linux@sandersweb.net> (raw)
In-Reply-To: <20081008125356.GA31684@infradead.org>

On Wednesday 08 October 2008 08:53:56 am Christoph Hellwig wrote:
> On Tue, Oct 07, 2008 at 05:20:02PM -0400, David Sanders wrote:
> > On Tuesday 07 October 2008 04:25:39 pm Adrian Bunk wrote:
> > > The 2.6.29 merge window will start in January - everything else is much
> > > more unlikely than an incompetent chick from Alaska getting only one
> > > heart attack away from the big red button.
> >
> > These comments are inappropriate for this list.
>
> Why?

I was talking about the Alaska chick thing.  The comment is wrong, but I 
didn't object to his politics, just the fact it was on the kernel developer's 
list.  The comments about the merge window are of course on topic.

  reply	other threads:[~2008-10-08 17:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 19:44 [RFC] Btrfs mainline plans Chris Mason
2008-10-03  7:18 ` Andrew Morton
2008-10-05 12:24   ` Adrian Bunk
2008-10-05 14:11     ` Serge E. Hallyn
2008-10-05 15:09       ` Adrian Bunk
2008-10-06 13:40         ` Chris Mason
2008-10-07 15:27           ` Adrian Bunk
2008-10-07 16:01             ` Chris Mason
2008-10-07 20:25               ` Adrian Bunk
2008-10-07 21:20                 ` David Sanders
2008-10-07 21:27                   ` Randy.Dunlap
2008-10-08 12:53                   ` Christoph Hellwig
2008-10-08 17:48                     ` David Sanders [this message]
2008-10-08 21:33         ` Daniel Phillips
2008-10-09  8:22           ` Adrian Bunk
2008-10-10  3:01             ` Theodore Tso
2008-10-03 17:06 ` Jan Engelhardt

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=200810081348.50710.linux@sandersweb.net \
    --to=linux@sandersweb.net \
    --cc=bunk@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 NNTP newsgroup(s).