From: Alex Coplan <alex.coplan@arm.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
binutils@sourceware.org, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Import mklog.py from gcc repo
Date: Fri, 18 Sep 2020 15:48:31 +0100 [thread overview]
Message-ID: <20200918144830.mjlmf2iplixirxec@arm.com> (raw)
In-Reply-To: <CAPTJ0XGj5pAe2mxkNKU4d+JpOwK6AUcRTSYO+X+HawwarBy9rA@mail.gmail.com>
On 18/09/2020 16:27, Christian Biesinger via Binutils wrote:
> On Thu, Sep 17, 2020 at 10:29 PM Simon Marchi via Gdb-patches
> <gdb-patches@sourceware.org> wrote:
> > The simplest way to fix this is to import the script in binutils-gdb and
> > use it from there. It's also nice because we can use it without having
> > a clone of the gcc repo.
>
> I like this in principle, but the one annoying part is that no longer
> prints the patch author/date line, so you have to manually create it.
> I suppose one could make their own script for that (or maybe emacs
> users have a macro for that or something)...
+1 to this, I've been using GCC's contrib/legacy/mklog for binutils for
this reason. Perhaps a flag could be added to mklog.py (or the binutils
version could be modified) to include author/date lines?
>
> Christian
Alex
next prev parent reply other threads:[~2020-09-18 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 20:29 Simon Marchi
2020-09-18 14:27 ` Christian Biesinger
2020-09-18 14:48 ` Alex Coplan [this message]
2020-09-18 14:50 ` Simon Marchi
2020-09-21 12:45 ` Martin Liška
2020-09-21 14:33 ` Simon Marchi
2020-09-21 15:31 ` Simon Marchi
2020-09-25 14:25 ` Simon Marchi
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=20200918144830.mjlmf2iplixirxec@arm.com \
--to=alex.coplan@arm.com \
--cc=binutils@sourceware.org \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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