From: Ben Greear <greearb@candelatech.com>
To: Andi Kleen <ak@suse.de>
Cc: netdev@oss.sgi.com
Subject: Re: Move fib_alias out of fib_hash.c
Date: Thu, 30 Sep 2004 08:51:26 -0700 [thread overview]
Message-ID: <415C2B7E.8060807@candelatech.com> (raw)
In-Reply-To: <20040930080810.GB20106@wotan.suse.de>
Andi Kleen wrote:
> There is no stable release cycle anymore. Linus has abolished that.
>
> Maybe we will get it back at some point if the current way doesn't
> work out, but currently it's unlimited hacking time.
Sounds fun for the programmers and a pain in the ass for everyone
else. But, maybe I can shove some of my patches into the tree with
less friction!
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2004-09-30 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 4:47 Move fib_alias out of fib_hash.c David S. Miller
2004-09-29 15:20 ` Robert Olsson
2004-09-29 19:53 ` David S. Miller
2004-09-29 21:20 ` Steven Blake
2004-09-29 21:27 ` David S. Miller
2004-09-29 22:09 ` Andi Kleen
2004-09-29 22:24 ` Ben Greear
2004-09-30 8:08 ` Andi Kleen
2004-09-30 15:51 ` Ben Greear [this message]
2004-09-29 21:43 ` Robert Olsson
2004-09-29 21:30 ` Robert Olsson
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=415C2B7E.8060807@candelatech.com \
--to=greearb@candelatech.com \
--cc=ak@suse.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).