This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 2/2] Introduce beginnings of a pipeline class.
- From: Martin Jambor <mjambor at suse dot cz>
- To: David Malcolm <dmalcolm at redhat dot com>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 25 Jul 2013 14:18:57 +0200
- Subject: Re: [PATCH 2/2] Introduce beginnings of a pipeline class.
- References: <1374678544-8678-1-git-send-email-dmalcolm at redhat dot com> <1374678544-8678-3-git-send-email-dmalcolm at redhat dot com> <CAD_=9DQiS+ALS31XiF1nqXsBUQF=X_w2_EpCzz38TWiwpk_t2g at mail dot gmail dot com> <CAD_=9DTY9XrfjfiAOq_o_vpYuENzdcz5OX+24zz6Y_kAGm+cpw at mail dot gmail dot com> <1374712063 dot 22936 dot 11 dot camel at surprise>
Hi,
On Wed, Jul 24, 2013 at 08:27:43PM -0400, David Malcolm wrote:
> On Wed, 2013-07-24 at 19:10 -0400, Diego Novillo wrote:
> > On Wed, Jul 24, 2013 at 6:56 PM, Diego Novillo <dnovillo@google.com> wrote:
> > > Could you please add a description of what this does?
> >
> > Sorry. You did, but in a previous message that I had managed to miss.
> > Maybe include a reference to it in future postings?
>
> FWIW I used "git format-patch" with the --cover-letter option and then
> put the bulk of the description in the cover letter i.e. the [PATCH 0/2]
> email i.e. http://gcc.gnu.org/ml/gcc-patches/2013-07/msg01088.html - is
> that what you're referring to, or to some other email (e.g. the
> discussion about passes.def in the other thread, which is:
> http://gcc.gnu.org/ml/gcc-patches/2013-07/msg01028.html )
>
> Is the cover letter and patch series approach OK for this list?
Yes it is, many people including me use similar setups, although
usually we put descriptions of individual patches at the top of the
message with the patch itself rather than to the cover letter. It is
more convenient for everyone, especially when the thread grows large
and much more convenient for people using clients like gmail which do
not thread and group messages with exactly the same subject instead.
Martin