From: Chewie <chewie@wookimus.net>
To: linux-lvm@msede.com
Subject: [linux-lvm] 0.9 next week?! Cool!
Date: Sat, 11 Nov 2000 12:11:51 -0600 [thread overview]
Message-ID: <20001111121151.B7541@wookimus.net> (raw)
In-Reply-To: <20001111131348.F32147@srv.t-online.de>; from Heinz.Mauelshagen@t-online.de on Sat, Nov 11, 2000 at 01:13:48PM +0000
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Sat, Nov 11, 2000 at 01:13:48PM +0000, Heinz J. Mauelshagen wrote:
> > How long will it take before 0.9 arrives?
> I am planing for next monday :-)
Woohoo! Thankyou, Heinz, for your hard work!
I have a request for you. *PLEASE* don't use odd version names like
0.9final, or Linus' faux paux with the "-test10-pre8" horror. ;-)
Have you considered using a kernel-like versioning rule, where the
minor (second) number is odd for development branch and even for the
stable branch. Yes, 0.7.131 may seem quite boring, but when 0.8 rolls
around, we'll know it's the first of the stable versions. Any 0.8.x
versions would obviously be patch fixes to the stable version.
Regardless, have you been holding out with 0.9 for so long because
you'd like it to be "stable" from its release point? With that in
mind, would you consider releasing 0.9 as 0.10?
Again, thanks!
--
Chad "^chewie, gunnarr" Walstrom <chewie@wookimus.net>
http://www.wookimus.net/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-11-11 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 10:18 [linux-lvm] 2.2.17 Kernel patch + 0.8 user tools dirk.derycke
2000-11-11 13:13 ` Heinz J. Mauelshagen
2000-11-11 18:11 ` Chewie [this message]
2000-11-12 15:29 ` [linux-lvm] 0.9 next week?! Cool! Heinz J. Mauelshagen
2000-11-11 17:59 ` [linux-lvm] 2.2.17 Kernel patch + 0.8 user tools Chewie
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=20001111121151.B7541@wookimus.net \
--to=chewie@wookimus.net \
--cc=linux-lvm@msede.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