From: Joe Pranevich <jpranevich@gmail.com>
To: Calvin Walton <calvin.walton@kepstin.ca>
Cc: Willy Tarreau <w@1wt.eu>, Mike Frysinger <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 3.0 change listings - Wonderful World of Linux 3.0
Date: Wed, 1 Jun 2011 20:03:41 -0400 [thread overview]
Message-ID: <BANLkTim7mGXzRhvnziyLBSULGYg2N+L0BA@mail.gmail.com> (raw)
In-Reply-To: <1306950434.3627.23.camel@ayu>
Hello,
Thank you for the feedback. While I already have a section about what
v3 means right at the top, I will be reworking the exuberance out of
the finished text, cutting the use of the word "new", and making it
more clear that this is a "v2.6 retrospective", to use your term. I
will also place notices to that effect on each page of the web version
of the doc. I think I have done a reasonable job in summarizing where
Linux has moved to since the last "dot-zero" release, which was my
hope and intent, and now I just want to move the text to make that
more clear.
This has been a good experience. I regularly follow kernel development
and read change logs, but there were still numerous things that I
learned about Linux 2.6.x that I didn't know. The wide angle lens
helped me and I hope it can help others. (My inclination, if I do this
again, would be to do a yearly writeup (WWOL 2012), though perhaps
we'll have yearly point releases anyway.)
I will finish these changes by Sunday. The doc may be too long for
another kernel post, but I appreciate the corrections and feedback so
please keep them coming.
Joe
On Wed, Jun 1, 2011 at 1:47 PM, Calvin Walton <calvin.walton@kepstin.ca> wrote:
> On Tue, 2011-05-31 at 22:13 +0200, Willy Tarreau wrote:
>> On Tue, May 31, 2011 at 01:22:49AM -0400, Joe Pranevich wrote:
>> > Mike,
>> >
>> > Thank you. I appreciate the comments and the corrections. It was a
>> > marathon weekend and yes, I missed some obvious typos. Thanks.
>> >
>> I'd say that in general, almost all of the features you're announcing as
>> "new" will make unaware people think that older versions did not have
>> those features, which is quite misleading. Linus took great care to say
>> that 3.0-rc1 had very few changes, it can be a bit confusing to see a
>> post pretending it to be a revolutionary new kernel.
>>
>> Probably that you should more clearly say that all those features were
>> progressively added in all 2.6 releases, otherwise I'm already expecting
>> to see a lot of idiocies posted in journals.
>
> Perhaps a simple change of the title and introduction would handle
> clearing this up. Instead of presenting it as a "What's new in Linux
> 3.0" article (which it is not, or it would be a lot shorter!), why not
> call it what it actually is: "A Retrospective of the Linux 2.6 era"?
>
> --
> Calvin Walton <calvin.walton@kepstin.ca>
>
>
next prev parent reply other threads:[~2011-06-02 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 19:59 Joe Pranevich
2011-05-31 3:16 ` Mike Frysinger
2011-05-31 5:22 ` Joe Pranevich
2011-05-31 5:48 ` david
2011-05-31 20:13 ` Willy Tarreau
2011-06-01 17:47 ` Calvin Walton
2011-06-02 0:03 ` Joe Pranevich [this message]
2011-05-31 15:23 ` Konrad Rzeszutek Wilk
2011-06-03 7:01 ` Jiri Slaby
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=BANLkTim7mGXzRhvnziyLBSULGYg2N+L0BA@mail.gmail.com \
--to=jpranevich@gmail.com \
--cc=calvin.walton@kepstin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.com \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®