public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "heming.zhao@suse.com" <heming.zhao@suse.com>
To: "Frank Ch. Eigler" <fche@redhat.com>,
	Overseers mailing list <overseers@sourceware.org>
Cc: LVM general discussion and development <linux-lvm@redhat.com>,
	Marian Csontos <mcsontos@redhat.com>
Subject: Re: [linux-lvm] how often does lvm team update source code in ftp site
Date: Mon, 10 Aug 2020 23:26:19 +0800	[thread overview]
Message-ID: <08580f21-d03c-d03e-ace2-29eeed588b1d@suse.com> (raw)
In-Reply-To: <20200810115232.GB1049@redhat.com>

Hello Marian & Frank,

Thank you for your information.

I got the (wrong) URL from: https://www.sourceware.org/lvm2/
In the section *Releases*.
It looks this webpage should be updated with: ftp://sourceware.org/pub/lvm2/

Thanks,

On 8/10/20 7:52 PM, Frank Ch. Eigler wrote:
> Hi -
> 
>>> 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?)
> 
> Please replace any references to the sources.redhat.com name with
> sourceware.org.  The former is a courtesy forward/mirror - we can't
> rely on any particular quality of service.
> 
> - FChE
> 


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A71F734D-C071-4CC7-A381-6FC11171B94C@gmail.com>
     [not found] ` <266c8ce7-9632-50fe-c440-ecde22c60e92@suse.com>
2020-08-10 10:22   ` Marian Csontos
2020-08-10 11:52     ` Frank Ch. Eigler
2020-08-10 15:26       ` heming.zhao [this message]
2020-08-10 15:44         ` Frank Ch. Eigler
2020-08-11 10:12           ` Marian Csontos
2020-08-11 12:29             ` Frank Ch. Eigler

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=08580f21-d03c-d03e-ace2-29eeed588b1d@suse.com \
    --to=heming.zhao@suse.com \
    --cc=fche@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=mcsontos@redhat.com \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).