From: Shahab Vahedi via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>,
Shahab Vahedi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Shahab Vahedi <shahab.vahedi@gmail.com>,
Tom Tromey <tom@tromey.com>,
Francois Bedard <Francois.Bedard@synopsys.com>
Subject: Re: [PUSHED gdb-10-branch] arc: Write correct "eret" value during register collection
Date: Fri, 4 Dec 2020 14:44:24 +0000 [thread overview]
Message-ID: <3af88f78-3d71-7986-e076-ccf2ddf85fbd@synopsys.com> (raw)
In-Reply-To: <20201204141012.GA151412@adacore.com>
Hi Joel,
Thank you for your kind nudge and sorry for messing it up. I have one question though:
On 12/4/20 3:10 PM, Joel Brobecker wrote:
>
> - Update the ChangeLog entry on both master and gdb-10-branch
> to include the PR number. E.g.
>
> | 2020-11-29 Hannes Domani <ssbssa@yahoo.de>
> |
> !!! -> | PR tui/26973
> | * tui/tui-layout.c (tui_apply_current_layout): Don't delete the
> | static locator win info.
The patch in "master" branch was submitted on 12-Nov-2020. Hence, its ChangeLog entry
is buried under other ones after 3 weeks. Is it OK if I just edit ChangeLog in "Master"
to update that entry back? Or is it only allowed to add things to top of ChangeLogs?
I think it should be OK, but I wanted to be sure.
--
Shahab
next prev parent reply other threads:[~2020-12-04 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 13:43 [PATCH] " Shahab Vahedi via Gdb-patches
2020-11-12 14:36 ` Tom Tromey
2020-11-12 15:46 ` Shahab Vahedi via Gdb-patches
2020-11-12 15:42 ` [PATCH v2] " Shahab Vahedi via Gdb-patches
2020-11-12 15:43 ` Tom Tromey
2020-11-12 16:05 ` [PUSHED] " Shahab Vahedi via Gdb-patches
2020-12-04 10:57 ` [PUSHED gdb-10-branch] " Shahab Vahedi via Gdb-patches
2020-12-04 14:10 ` Joel Brobecker
2020-12-04 14:44 ` Shahab Vahedi via Gdb-patches [this message]
2020-12-04 14:53 ` Joel Brobecker
2020-12-04 15:38 ` Shahab Vahedi via Gdb-patches
2020-12-05 8:12 ` Joel Brobecker
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=3af88f78-3d71-7986-e076-ccf2ddf85fbd@synopsys.com \
--to=gdb-patches@sourceware.org \
--cc=Francois.Bedard@synopsys.com \
--cc=Shahab.Vahedi@synopsys.com \
--cc=brobecker@adacore.com \
--cc=shahab.vahedi@gmail.com \
--cc=tom@tromey.com \
/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