linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Gang He <GHe@suse.com>
To: David Teigland <teigland@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] dlm userspace tool source tarball name format has been changed to dlm-dlm-4.0.x.tar.gz
Date: Thu, 8 Aug 2019 02:15:50 +0000	[thread overview]
Message-ID: <CH2PR18MB32060E1DC8E5D58A5CE75D1BCFD70@CH2PR18MB3206.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190807170526.GB32348@redhat.com>

Hi David,

If I download the source code tar-ball from https://releases.pagure.org/dlm/, the tar-ball file names looks the same with the before.
If I download the source code tar-ball from https://pagure.io/dlm/releases (e.g. https://pagure.io/dlm/archive/dlm-4.0.9/dlm-dlm-4.0.9.tar.gz),
the tar-ball file name format looks changed.
So, which link is the official dlm release download link?

Thanks
Gang 

> -----Original Message-----
> From: David Teigland [mailto:teigland@redhat.com]
> Sent: 2019��8��8�� 1:05
> To: Gang He <GHe@suse.com>
> Cc: LVM general discussion and development <linux-lvm@redhat.com>
> Subject: Re: [linux-lvm] dlm userspace tool source tarball name format has
> been changed to dlm-dlm-4.0.x.tar.gz
> 
> On Wed, Aug 07, 2019 at 04:33:24AM +0000, Gang He wrote:
> > Hi David,
> >
> > Today, I downloaded the dlm user-space tool source code tar-ball from
> https://pagure.io/dlm.
> > I found the tar-ball name format has been changed to dlm-dlm-4.0.x.tar.gz,
> the newly added "dlm-" prefix name is on purpose?
> 
> I uploaded a correctly named file to https://releases.pagure.org/dlm/ pagure
> automatically adds the redundant prefix to generated files.
> 

  reply	other threads:[~2019-08-08  2:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  4:33 [linux-lvm] dlm userspace tool source tarball name format has been changed to dlm-dlm-4.0.x.tar.gz Gang He
2019-08-07 17:05 ` David Teigland
2019-08-08  2:15   ` Gang He [this message]
2019-08-08 14:35     ` David Teigland

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=CH2PR18MB32060E1DC8E5D58A5CE75D1BCFD70@CH2PR18MB3206.namprd18.prod.outlook.com \
    --to=ghe@suse.com \
    --cc=linux-lvm@redhat.com \
    --cc=teigland@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).