linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 'Goldwyn Rodrigues' <rgoldwyn@suse.de>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: 'LKML' <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, 'Hyunchul Lee' <hyc.lee@gmail.com>,
	'Eric Sandeen' <sandeen@sandeen.net>,
	'Sedat Dilek' <sedat.dilek@gmail.com>
Subject: Re: [ANNOUNCE] exfatprogs-1.0.2 version released
Date: Thu, 23 Apr 2020 21:32:55 -0500	[thread overview]
Message-ID: <20200424023255.a4gcjpy5ebkfzi2z@fiona> (raw)
In-Reply-To: <000101d619c8$5c6e3b90$154ab2b0$@samsung.com>

Hi Namjae,

On  8:38 24/04, Namjae Jeon wrote:

<snip>

> > >
> > > The tarballs can be found at:
> > >
> > > https://protect2.fireeye.com/url?k=88473660-d58d03d7-8846bd2f-0cc47a30
> > > 03e8-7bb3906eafbb32bc&q=1&u=https%3A%2F%2Fgithub.com%2Fexfatprogs%2Fex
> > > fatprogs%2Freleases%2Ftag%2F1.0.2
> > >
> > 
> > Can we follow the standard of source tarballs be <projectname>-<version>.tar.gz? In this case, exfat-
> > 1.0.2.tar.gz instead of 1.0.2.tar.gz?
> Ah, When I tried to download it through this link, source tarballs was exfatprogs-1.0.2.tar.gz...
> Am I missing something ?

The filename on the link is:
https://github.com/exfatprogs/exfatprogs/archive/1.0.2.tar.gz

When I extract it, it extracts to exfatprogs-1.0.2 though.

-- 
Goldwyn

      reply	other threads:[~2020-04-24  2:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200423084908epcas1p1b5d43c33b263b30844fc03a341f67413@epcas1p1.samsung.com>
2020-04-23  8:49 ` [ANNOUNCE] exfatprogs-1.0.2 version released Namjae Jeon
2020-04-23 13:43   ` Eric Sandeen
2020-04-23 23:35     ` Namjae Jeon
2020-04-23 14:44   ` 'Goldwyn Rodrigues'
2020-04-23 14:55     ` Eric Sandeen
2020-04-23 23:38     ` Namjae Jeon
2020-04-24  2:32       ` 'Goldwyn Rodrigues' [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=20200424023255.a4gcjpy5ebkfzi2z@fiona \
    --to=rgoldwyn@suse.de \
    --cc=hyc.lee@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=sandeen@sandeen.net \
    --cc=sedat.dilek@gmail.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).