From: Tom Tromey <tom@tromey.com>
To: Branislav Brzak <Branislav.Brzak@Syrmia.com>
Cc: Tom Tromey <tom@tromey.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Dragoslav Sicarov <Dragoslav.Sicarov@Syrmia.com>,
Djordje Todorovic <Djordje.Todorovic@syrmia.com>
Subject: Re: [PATCH 0/1] riscv: Ensure LE instruction fetching
Date: Thu, 06 Jul 2023 10:13:52 -0600 [thread overview]
Message-ID: <877crdc91b.fsf@tromey.com> (raw)
In-Reply-To: <AM6PR03MB49849A2E738FC58BCCEB84ED985DA@AM6PR03MB4984.eurprd03.prod.outlook.com> (Branislav Brzak's message of "Wed, 21 Jun 2023 09:11:13 +0000")
> I'd like to do the commit myself, although I'm having some issues.
> Namely, I've been following this guide https://sourceware.org/gdb/wiki/PushingToReleaseBranch
> and I have the bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=30571
> And locally I have the commit in the specified format.
I'm checking this in for you.
The commit message on the actual patch was just a changelog entry. gdb
doesn't use changelog any more, and it's better to write a descriptive
subject and text, so I took these from the "PATCH 0/0" email you sent.
Normally what I do for single patches is just use the commit message
directly as the email. This helps ensure that sufficient information is
in there. Then I "git send-email" instead of attaching it.
Tom
prev parent reply other threads:[~2023-07-06 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 11:46 Branislav Brzak
2023-06-20 11:47 ` Branislav Brzak
2023-06-20 14:08 ` Tom Tromey
2023-06-20 14:21 ` Branislav Brzak
2023-06-20 16:42 ` Tom Tromey
2023-06-21 9:11 ` Branislav Brzak
2023-07-06 16:13 ` Tom Tromey [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=877crdc91b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Branislav.Brzak@Syrmia.com \
--cc=Djordje.Todorovic@syrmia.com \
--cc=Dragoslav.Sicarov@Syrmia.com \
--cc=gdb-patches@sourceware.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).