From: Simon Marchi <simark@simark.ca>
To: Hans-Peter Nilsson <hp@bitrange.com>, Jan Dubiec <jdx@o2.pl>
Cc: Jan Beulich <jbeulich@suse.com>,
binutils@sourceware.org, gdb-patches@sourceware.org,
Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH v3] h8300-elf: ld: Use USER_LABEL_PREFIX when generating linker scripts [REPOST]
Date: Thu, 17 Sep 2026 09:18:36 -0400 [thread overview]
Message-ID: <f325ffd2-5093-4691-abc1-e667aeba612a@simark.ca> (raw)
In-Reply-To: <alpine.BSF.2.20.16.2609170555310.70026@arjuna.pair.com>
On 9/17/26 6:02 AM, Hans-Peter Nilsson wrote:
> On Thu, 17 Sep 2026, Jan Dubiec wrote:
>> On 16.09.2026 16:58, Simon Marchi wrote:
>> [...]> Looks like the change was OK'ed by the relevant people. However, could
>>> you please make the commit message actually describe the change?
>>>
>>> Thanks,
>>>
>>> Simon
>>
>> I am not sure how the commit message should be posted, so here it is.
>
> The usual way is that you, after editing the commit message and
> amending the commit, send it together with the rest of the
> patch, in form of an in-line copy of the file generated by "git
> format-patch [...]".
And / or git-send-email.
> But the below works and LGTM, so ok.
>
>> I hope
>> it will not be a problem for whoever commits the patch to copy and paste the
>> message below.
>
> Oh, you don't have commit rights. I'll do it, if no-one beats
> me to it.
Thanks, please go ahead.
Simon
prev parent reply other threads:[~2026-09-17 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 20:10 Jan Dubiec
2026-08-24 0:52 ` Alan Modra
2026-09-15 9:16 ` [PING] " Jan Dubiec
2026-09-16 4:46 ` Hans-Peter Nilsson
2026-09-16 14:58 ` Simon Marchi
2026-09-17 0:48 ` Hans-Peter Nilsson
2026-09-17 7:28 ` Jan Dubiec
2026-09-17 10:02 ` Hans-Peter Nilsson
2026-09-17 13:18 ` Simon Marchi [this message]
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=f325ffd2-5093-4691-abc1-e667aeba612a@simark.ca \
--to=simark@simark.ca \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=hp@bitrange.com \
--cc=jbeulich@suse.com \
--cc=jdx@o2.pl \
/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