Re: [RESEND] [PATCH 1/12] PPC64: First in the series of patches implementing POWER8 vector math.

[GT <tnggil at protonmail dot com>]

> > 4.  Changed patch subject line to now include m/n sequence indicator.
>
> Could you also use the "git format-patch -v" convention for distinguishing
> the version of the patch series? So if it's version 10 (I haven't counted
> how many there have been), it would be "[PATCH v10 1/12]", for example (no
> "[RESEND]", please).
>

So; trying to find all patch versions and the comments that have
accompanied each got me to thinking this:

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 way, there will be only one git object to examine in order to see what
has been discussed regarding any patch. Instead of what is now a manual
search through the mailing list.

Yes/No?

Thanks.
Bert.