From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3D40AC433E0 for ; Thu, 2 Jul 2020 04:57:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 10EFC207D4 for ; Thu, 2 Jul 2020 04:57:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="SoIMie4g" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726196AbgGBE5u (ORCPT ); Thu, 2 Jul 2020 00:57:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43732 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725994AbgGBE5s (ORCPT ); Thu, 2 Jul 2020 00:57:48 -0400 Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ED336C08C5C1; Wed, 1 Jul 2020 21:57:47 -0700 (PDT) Received: by mail-vs1-xe34.google.com with SMTP id q15so3816093vso.9; Wed, 01 Jul 2020 21:57:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=+0bMkjlNweJe9TFHPH7QDbYYIlGusfAJZ/4YOX6Udzc=; b=SoIMie4goVN84DWDKrrQhScJzlrtyk3eda4km0biJrrMKMlO2hXLTjzq1qRYcjsqfR J1KAs49bOFxAEXjkEHD3JVmST2xHDQwi3396NfQiVGTRpjvER5x4L0v7tK/tcnRldzB9 vM6fuzWPJyspAQvxW9WsZJJyG4zpAMlCYLZUnOlpR8zF9VftwChCBfRhZR6yGYOqZdrv lUi2oF+6esFFpnmOVRAmN4AiQ23qJMMsMjVRPDX+mNZzcoxsLV8qjCjnJAFxutj8Bcwm Vyb9LZ1ak4EiacmeKs7DhSXnpf+5RQ/kADHxN3n5vR9giESkbe/lf/XB0rC1VbammrEO fWLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=+0bMkjlNweJe9TFHPH7QDbYYIlGusfAJZ/4YOX6Udzc=; b=CDkAl3lGs/yOsHCO4rFfqzX4qg3gMnxlv4eddXLinmmgHNNI/C3nkjnFaaJIZcLx2z xC/vAkLtkOWLqwUvy6QlofSA6Xhi8W3PMRVQwOQGFTO8CDGYpzoTY/FCAeOZOKZlIok1 V7FKryXg9NuQExKcumceAmkup6Vvxb9Gwy7fmuGF1IO/bsbB7U+WFgsQ/SdN0jz3m7Ff Dk4pVPmHaMKIHyI0p87nWQw6tuU1BglEiBOoJ+CWtmPpI/Bkz6aV+gmoyKtYkFO2qVVN 7lA2W44TwOldGktBBADUmC6C+vSQRXvhB6sZuL1dU267oq6rJexu8Bi6CovQkG0kUp1Z svLA== X-Gm-Message-State: AOAM530ZCY/LQXgzBAxDoBeqbUYQachdUlNTWce6daeVIL1TFCh910pV XIfgmd98ZHtP4CZ6nW1GzqNxILutheionpFuoyo= X-Google-Smtp-Source: ABdhPJy9NjgQQmaoE8GisXsEmJ3aGETwcyd72wUMMPxGQSA0S/P3mvAOMMCkXSX6wJYW4bdBwbWUaHacBwCdGY4n6Yk= X-Received: by 2002:a67:ed02:: with SMTP id l2mr21816075vsp.137.1593665866885; Wed, 01 Jul 2020 21:57:46 -0700 (PDT) MIME-Version: 1.0 References: <000201d62835$7ddafe50$7990faf0$@samsung.com> In-Reply-To: From: Hyunchul Lee Date: Thu, 2 Jul 2020 13:57:36 +0900 Message-ID: Subject: Re: exfatprogs-1.0.3 version released To: sedat.dilek@gmail.com Cc: Namjae Jeon , Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, Eric Sandeen , Goldwyn Rodrigues , Nicolas Boos Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Sedat, For v1.0.3 and later releases, we can provide tar.xz tarballs, hashes and detached signatures. But is there a reason why hashes are required despite the signature? We will let you know when it's done. Thanks. Regards, Hyunchul 2020=EB=85=84 6=EC=9B=94 30=EC=9D=BC (=ED=99=94) =EC=98=A4=ED=9B=84 7:16, S= edat Dilek =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1: > > On Tue, May 12, 2020 at 10:17 AM Namjae Jeon wr= ote: > > > > Hi folk, > > > > We have released exfatprogs-1.0.3 version. > > Any feedback is welcome!:) > > > > CHANGES : > > * Rename label.exfat to tune.exfat. > > * tune.exfat: change argument style(-l option for print level, > > -L option for setting label) > > * mkfs.exfat: harmonize set volume label option with tune.exfat. > > > > NEW FEATURES : > > * Add man page. > > > > BUG FIXES : > > * Fix the reported build warnings/errors. > > * Add memset to clean garbage in allocation. > > * Fix wrong volume label array size. > > * Open a device using O_EXCL to avoid formatting it while it is mounte= d. > > * Fix incomplete "make dist" generated tarball. > > > > The git tree is at: > > https://github.com/exfatprogs/exfatprogs > > > > The tarballs can be found at: > > https://github.com/exfatprogs/exfatprogs/releases/download/1.0.3/= exfatprogs-1.0.3.tar.gz > > > > Hi, > > thanks for the upgrade. > > Today, I contacted the Debian maintainer on how he wants to > distinguish between exfat-utils vs. exfatprogs as Linux v5.7 entered > Debian/unstable. > > When I looked at the release/tags page on github: > > Can you please offer tar.xz tarballs, please? > Hashes? Like sha256sum > Signing keys? (Signed tarballs?) > > Thanks. > > Regards, > - Sedat -