From: Joseph Myers <joseph@codesourcery.com>
To: Egeyar Bagcioglu <egeyar.bagcioglu@oracle.com>
Cc: <gcc-patches@gcc.gnu.org>, <mliska@suse.cz>,
<segher@kernel.crashing.org>
Subject: Re: [PATCH v2 0/3] Introduce a new GCC option, --record-gcc-command-line
Date: Tue, 03 Mar 2020 22:57:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2003032252390.24902@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1583246660-6390-1-git-send-email-egeyar.bagcioglu@oracle.com>
On Tue, 3 Mar 2020, Egeyar Bagcioglu wrote:
> Although we discussed after the submission of the first version that
> there are several other options performing similar tasks, I believe we
> established that there is still a need for this specific functionality.
> Therefore, I am skipping in this email the comparison between this
> option and the existing options with similarities.
We're now using git-style commit messages with self-contained explanation
/ justification of the change being committed.
This means that one of the commit messages (not just message 0, whose
contents don't go in a commit message) for an individual patch should have
the explanation, which should include the self-contained justification by
reference to comparison with other existing similar options. People
should be able to find the relevant information in the commit without
needing to search the list archives for reviews of a previous patch
version.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-03-03 22:57 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 16:41 Egeyar Bagcioglu
2020-03-03 16:41 ` [PATCH v2 2/3] Introduce the gcc option --record-gcc-command-line Egeyar Bagcioglu
2020-03-03 16:41 ` [PATCH v2 1/3] Introduce dg-require-target-object-format Egeyar Bagcioglu
2020-03-03 16:41 ` [PATCH v2 3/3] Keep .GCC.command.line sections of LTO objetcs Egeyar Bagcioglu
2020-03-04 9:01 ` Richard Biener
2020-03-04 15:26 ` Egeyar Bagcioglu
2020-03-04 17:23 ` Martin Liška
2020-03-04 17:33 ` Jakub Jelinek
2020-03-04 17:42 ` Martin Liška
2020-03-04 17:47 ` Jakub Jelinek
2020-03-04 22:43 ` Egeyar Bagcioglu
2020-03-05 8:54 ` Martin Liška
2020-03-05 13:17 ` Egeyar Bagcioglu
2020-03-17 13:53 ` [stage1][PATCH] Change semantics of -frecord-gcc-switches and add -frecord-gcc-switches-format Martin Liška
2020-03-17 18:43 ` Egeyar Bagcioglu
2020-03-18 9:05 ` Martin Liška
2020-04-03 18:15 ` Egeyar Bagcioglu
2020-04-06 7:09 ` Martin Liška
2020-05-15 9:58 ` Martin Liška
2020-06-02 9:16 ` Martin Liška
2020-06-16 12:49 ` Martin Liška
2020-07-21 16:24 ` Qing Zhao
2020-07-23 10:07 ` Martin Liška
2020-07-23 15:01 ` Qing Zhao
2020-07-24 13:43 ` Martin Liška
2020-09-25 14:55 ` Martin Liška
2020-09-25 19:36 ` Qing Zhao
2020-10-27 10:56 ` Martin Liška
2020-11-10 20:53 ` Qing Zhao
2020-11-13 16:19 ` Jose E. Marchesi
2020-11-16 10:29 ` Martin Liška
2020-11-16 17:03 ` Qing Zhao
2020-11-20 9:49 ` Richard Biener
2020-11-23 8:59 ` Martin Liška
2020-11-23 11:00 ` Richard Biener
2020-11-23 13:02 ` Martin Liška
2020-11-23 14:52 ` Martin Liška
2020-11-25 13:48 ` Richard Biener
2020-11-26 13:55 ` Martin Liška
2020-12-02 10:46 ` Martin Liška
2020-12-03 13:12 ` Richard Biener
2020-12-04 8:08 ` Martin Liška
2020-12-04 9:03 ` Richard Biener
2020-12-04 13:30 ` Martin Liška
2020-12-04 13:34 ` Jakub Jelinek
2020-12-04 13:50 ` Richard Biener
2020-12-15 8:01 ` [PATCH 1/2] Remove Report keyword for options Martin Liška
2020-12-15 8:02 ` [PATCH 2/2] opts: Remove all usages of Report keyword Martin Liška
2020-12-15 19:43 ` Jeff Law
2020-12-15 21:21 ` Martin Liška
2020-12-15 19:42 ` [PATCH 1/2] Remove Report keyword for options Jeff Law
2020-12-16 11:46 ` Martin Liška
2021-01-06 14:21 ` [stage1][PATCH] Change semantics of -frecord-gcc-switches and add -frecord-gcc-switches-format Martin Liška
2021-01-14 9:03 ` Martin Liška
2021-01-22 13:33 ` Martin Liška
2021-01-29 13:35 ` Martin Liška
2021-02-05 9:34 ` [PATCH] " Martin Liška
2021-02-16 21:17 ` Qing Zhao
2021-02-18 9:18 ` Martin Liška
2021-03-01 12:07 ` Martin Liška
2021-03-12 12:39 ` Martin Liška
2021-01-15 19:14 ` [stage1][PATCH] " Alexandre Oliva
2021-01-18 9:03 ` Martin Liška
2020-03-04 19:39 ` [PATCH v2 3/3] Keep .GCC.command.line sections of LTO objetcs Egeyar Bagcioglu
2020-03-05 7:40 ` Richard Biener
2020-03-04 15:34 ` Andreas Schwab
2020-03-04 15:58 ` Egeyar Bagcioglu
2020-03-03 17:43 ` [PATCH v2 0/3] Introduce a new GCC option, --record-gcc-command-line Egeyar Bagcioglu
2020-03-03 22:57 ` Joseph Myers [this message]
2020-03-04 0:18 ` Fangrui Song
2020-03-04 16:28 ` Egeyar Bagcioglu
2020-03-04 16:51 ` Egeyar Bagcioglu
2020-03-05 7:36 ` Richard Biener
2020-03-05 13:43 ` Egeyar Bagcioglu
2020-03-04 9:07 ` Martin Liška
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2003032252390.24902@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=egeyar.bagcioglu@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).