From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2 tarballs vanishing
Date: Wed, 7 Sep 2016 18:41:51 +0200 [thread overview]
Message-ID: <07804262-5ad5-4c24-f5ee-e0e97c41a4d3@gmail.com> (raw)
In-Reply-To: <20160907092945.GG2480@suse.de>
Dne 7.9.2016 v 11:29 Marcus Meissner napsal(a):
> Hi,
>
> Is there a specific reasons that old LVM2 tarballs are removed from
> ftp://sources.redhat.com/pub/lvm2/
>
> e.g. there are wide gaps in the series 133-143 144-147 147-152 152-154 154-162 162-165
>
Yep, some releases are 'developmental' check-points,
others were found with some rather 'unwanted' bugs/features.
Anyway if you still really want to get those
'obsoleted'/'unsupportable'/'broken' (pick the word you like) files for
studying purpose - see:
ftp://sources.redhat.com/pub/lvm2/releases/
eventually use git with proper tag v2_02_XXX
But please never-ever try to do any distro release with those tarballs....
Regards
Zdenek
prev parent reply other threads:[~2016-09-07 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 9:29 [linux-lvm] lvm2 tarballs vanishing Marcus Meissner
2016-09-07 16:41 ` Zdenek Kabelac [this message]
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=07804262-5ad5-4c24-f5ee-e0e97c41a4d3@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-lvm@redhat.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).