From: Marian Csontos <mcsontos@redhat.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
"heming.zhao@suse.com" <heming.zhao@suse.com>
Subject: Re: [linux-lvm] how often does lvm team update source code in ftp site
Date: Tue, 11 Aug 2020 12:12:59 +0200 [thread overview]
Message-ID: <03cc0d27-7182-aaa1-f42e-d0144c45ae57@redhat.com> (raw)
In-Reply-To: <20200810154447.GC70288@elastic.org>
On 8/10/20 5:44 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> 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/
>
> I tried a couple of ways to edit the lvm2 web pages to fix these
> links, but I'm foiled by git-hook scripts and stuff, so I'll leave it
> to AGK etc.
I have updated some of the links. Checked the rest.
There is a link to CVS web interface:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/?cvsroot=lvm2
This redirects to:
https://sourceware.org/viewvc
and I am getting 403 Forbidden.
I checked other projects (via google), found ecos at sw.o having same
problem.
I can still check out the CVS code fine.
Is there a working CVS interface or shall I remove that link?
-- Martian
>
> - FChE
>
> _______________________________________________
> 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/
>
next prev parent reply other threads:[~2020-08-11 10:13 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
2020-08-10 15:44 ` Frank Ch. Eigler
2020-08-11 10:12 ` Marian Csontos [this message]
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=03cc0d27-7182-aaa1-f42e-d0144c45ae57@redhat.com \
--to=mcsontos@redhat.com \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=heming.zhao@suse.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).