[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 21 Jun 2023 10:44:21 -0400
From: Rich Felker <dalias@...c.org>
To: 罗勇刚(Yonggang Luo) <luoyonggang@...il.com>
Cc: Musl <musl@...ts.openwall.com>
Subject: Re: [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@...c.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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
