This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RESEND] [PATCH 1/12] PPC64: First in the series of patches implementing POWER8 vector math.
- From: Joseph Myers <joseph at codesourcery dot com>
- To: GT <tnggil at protonmail dot com>
- Cc: "libc-alpha\\@sourceware.org" <libc-alpha at sourceware dot org>
- Date: Fri, 8 Mar 2019 23:23:29 +0000
- Subject: Re: [RESEND] [PATCH 1/12] PPC64: First in the series of patches implementing POWER8 vector math.
- References: <SLqh7MJvtXAa1Y5dfAS32jhZvA2XNtQLmNWcAyggITb-D0YPGLXvJ34fDpGxEIP8AsVlLcHx-V3d50_rrM5M2czbrxmWDtdvKV5bkTODvjY=@protonmail.com> <alpine.DEB.2.21.1903071904500.16241@digraph.polyomino.org.uk> <TDklchrZcWwACxBK0JVbZOd1tpwJi2kC3hZuwFEmR3M6k3sMOoy0Ekgmm271K7r4ApT9O2Z50RgdwhdRZqE5JswiTyAol4jsttjt8mCUjvg=@protonmail.com>
On Fri, 8 Mar 2019, GT wrote:
> 1. Could we use git to keep the procedure simpler and cleaner? By having
> the first version of a patch to libc-alpha committed to a public repo. Then,
> anyone who wants to comment on that patch clones/fetches from the repo. and
> modifies ONLY the notes that go along with the patch. Then sends the modified
> patch to libc-alpha, after which the owner of the repo. pushes the patch now
> containing new commentary. Repeated for each new comment.
That's a lot more complicated than simply replying to emails. (Putting
the full commit message and patch contents in the email body rather than
an attachment also helps make patch review by replying to patch emails as
easy as possible, but putting the patch contents there requires an email
client that won't modify whitespace in those patch contents at all, or
using git itself for sending the emails.)
The process, of emailing successive revisions of patch series, is somewhat
similar to that used by the Linux kernel, which various git commands
(rebase, format-patch, etc.) are designed to facilitate. (There are of
course some differences from Linux kernel processes as well.)
--
Joseph S. Myers
joseph@codesourcery.com