From: Erik Logtenberg <erik@logtenberg.eu>
To: diegocg@gmail.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: version (was: btrfs, broken design?)
Date: Wed, 26 Jan 2011 11:13:20 +0100 [thread overview]
Message-ID: <4D3FF3C0.5060505@logtenberg.eu> (raw)
In-Reply-To: <201101211532.56140.diegocg@gmail.com>
On 01/21/2011 03:32 PM, Diego Calleja wrote:
> On Viernes, 21 de Enero de 2011 10:54:00 Helmut Hullen escribi=F3:
>=20
>> And I never have seen somethin like "Changelog" - that would be fine=
=20
>> too.
>=20
> Check the wiki, I keep that updated: https://btrfs.wiki.kernel.org/in=
dex.php/Main_Page#News
I like the Changelog on the wiki [1] very much, since it shows the most
important changes in easily understandable language. Unfortunately, the
most recent change is 2.6.35 (august 2010), while we are currently at
2.6.37 (stable) and 2.6.38-rc2 (mainline). Especially 2.6.38(-rc2)
contains many interesting new btrfs features and lots of important
fixes. It would be very nice if the Changelog could list/explain those.
[1] https://btrfs.wiki.kernel.org/index.php/Changelog
The News [2] section on the Main page does mention one more version,
2.6.37. But the news section is less elaborate than the Changelog and
also I notice that 2.6.36 is not mentioned in the News section. Still,
2.6.36 does contain all kinds of btrfs-related changes.
[2] https://btrfs.wiki.kernel.org/index.php/Main_Page#News
Diego, pls don't read anything negative in my comments, I enjoy and
respect your work very much! If you could find time to add those latest
changes to the wiki, it would be greatly appreciated.
Kind regards,
Erik.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-26 10:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 21:06 btrfs, broken design? Benoît Thiébault
2011-01-20 21:20 ` Chris Mason
2011-01-21 5:25 ` Benoît Thiébault
2011-01-21 6:46 ` Chester
2011-01-21 8:11 ` Benoît Thiébault
2011-01-21 8:21 ` Hubert Kario
2011-01-21 9:54 ` version (was: btrfs, broken design?) Helmut Hullen
2011-01-21 12:21 ` Hugo Mills
2011-01-21 14:10 ` version Helmut Hullen
2011-01-21 14:32 ` version (was: btrfs, broken design?) Diego Calleja
2011-01-21 14:55 ` version Helmut Hullen
2011-01-21 15:12 ` version Hugo Mills
2011-01-21 15:19 ` version Helmut Hullen
2011-01-24 3:20 ` version Chris Samuel
2011-01-24 8:33 ` version Helmut Hullen
2011-01-24 21:14 ` version Johannes Hirte
2011-01-24 21:39 ` version Helmut Hullen
2011-01-24 22:46 ` version Chris Samuel
2011-01-25 1:03 ` version Chris Mason
2011-01-25 6:43 ` version Helmut Hullen
2011-01-25 14:37 ` version Helmut Hullen
2011-01-27 5:02 ` 2.6.38-rc2 oops's when rebalancing on different size drives (was Re: version) Chris Samuel
2011-01-27 7:45 ` version Chris Mason
2011-01-27 8:16 ` version Helmut Hullen
2011-01-27 13:28 ` version Helmut Hullen
2011-01-27 13:49 ` no space left (was: version) Helmut Hullen
2011-01-26 10:13 ` Erik Logtenberg [this message]
2011-01-26 14:13 ` version (was: btrfs, broken design?) Diego Calleja
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=4D3FF3C0.5060505@logtenberg.eu \
--to=erik@logtenberg.eu \
--cc=diegocg@gmail.com \
--cc=linux-btrfs@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).