linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Marian Csontos <mcsontos@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: overseers@sourceware.org, "heming.zhao@suse.com" <heming.zhao@suse.com>
Subject: Re: [linux-lvm] how often does lvm team update source code in ftp site
Date: Mon, 10 Aug 2020 12:22:09 +0200	[thread overview]
Message-ID: <2b204b75-5fe5-5af3-cf88-85f920e9fa2c@redhat.com> (raw)
In-Reply-To: <266c8ce7-9632-50fe-c440-ecde22c60e92@suse.com>

On 8/10/20 11:36 AM, heming.zhao@suse.com wrote:
> Hello,
> 
> I have a question about the release freq.
> The lvm2 2.03.10 tag had been created on yesterday
> But in ftp site: ftp://sources.redhat.com/pub/lvm2/releases > The latest lvm2 version is 2.03.05.

Hi, seems something went wrong with syncing sourceware.org and 
sources.redhat.com. (Or am I doing someting wrong, overseers?)

You can look at ftp://sourceware.org/pub/lvm2/ and get the tarballs there.

-- Martian

> 
> How often does lvm2 team update for this site?
> Or are there some reasons/rules for not putting latest packages in this site?
> 
> Thanks,
> heming
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 

  reply	other threads:[~2020-08-10 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09 23:19 [linux-lvm] what will happen with lvconvert merge after reboot? Tomas Dalebjörk
2020-08-10  9:36 ` [linux-lvm] how often does lvm team update source code in ftp site heming.zhao
2020-08-10 10:22   ` Marian Csontos [this message]
     [not found]     ` <20200810115232.GB1049@redhat.com>
2020-08-10 15:26       ` heming.zhao
2020-08-10 15:44         ` Frank Ch. Eigler
2020-08-10 15:24 ` [linux-lvm] what will happen with lvconvert merge after reboot? Zdenek Kabelac

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=2b204b75-5fe5-5af3-cf88-85f920e9fa2c@redhat.com \
    --to=mcsontos@redhat.com \
    --cc=heming.zhao@suse.com \
    --cc=linux-lvm@redhat.com \
    --cc=overseers@sourceware.org \
    --subject='Re: [linux-lvm] how often does lvm team update source code in ftp site' \
    /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

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).