From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_LOW,T_SCC_BODY_TEXT_LINE autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 17452 invoked from network); 21 Jun 2023 14:44:37 -0000
Received: from second.openwall.net (193.110.157.125)
  by inbox.vuxu.org with ESMTPUTF8; 21 Jun 2023 14:44:37 -0000
Received: (qmail 31904 invoked by uid 550); 21 Jun 2023 14:44:34 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 31865 invoked from network); 21 Jun 2023 14:44:33 -0000
Date: Wed, 21 Jun 2023 10:44:21 -0400
From: Rich Felker <dalias@libc.org>
To: =?utf-8?B?572X5YuH5YiaKFlvbmdnYW5nIEx1byk=?= <luoyonggang@gmail.com>
Cc: Musl <musl@lists.openwall.com>
Message-ID: <20230621144421.GJ4163@brightrain.aerifal.cx>
References: <20230620143703.1415-1-luoyonggang@gmail.com>
 <20230620224704.GI4163@brightrain.aerifal.cx>
 <CAE2XoE_wy2dsgcBrQTVgirzcwsW5R1sFj1MoZBbDDDuKMMUReA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAE2XoE_wy2dsgcBrQTVgirzcwsW5R1sFj1MoZBbDDDuKMMUReA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] [PATCH v3 0/5] Add posix/pthread_mutex_clocklock
 posix/pthread_cond_clockdwait c2y/mtx_timedlock_base c2y/cnd_timedwait_base

On Wed, Jun 21, 2023 at 02:25:58PM +0800, 罗勇刚(Yonggang Luo) wrote:
> On Wed, Jun 21, 2023 at 6:47 AM Rich Felker <dalias@libc.org> wrote:
> > As a general principle, please groups of associated patches to this
> > list as a single mail with the individual patches as MIME attachments,
> > not LKML-style as a giant thread with one message per patch. This is
> > to:
> 
> LKML-style patches are generally used, what makes musl should not use that?
> If email is the only way to submit patches for musl, I think LKML-style
> patches have general agreement,
> otherwise it's better to use github/gitlab to do that.
> Because the LKML-style patches can be sent by using `git git-send-email` to
> do that.
> So the following reasons is not a issue for glibc/linux/qemu and so on,
> they have much larger volume.

It's not the way we do things here, and I explained why. git has an
equally easy (arguably easier since it doesn't require the git command
to invoke your mail tools) way to do patches as attachments.

    git format-patch -4

will produce files 0001-...patch, 0002-...patch, 0003-...patch,
0004-...patch for the last 4 commits (replace 4 with whatever number
you need) which can then be attached via whatever method you normally
use in your mail software.

Rich