From: Yao Qi <qiyaoltc@gmail.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: gdb-patches@sourceware.org, Yao Qi <yao.qi@linaro.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH v2] PR breakpoints/21886: mem-break: Fix breakpoint insertion location
Date: Fri, 11 Aug 2017 15:12:00 -0000 [thread overview]
Message-ID: <20170811151238.GI8039@1170ee0b50d5> (raw)
In-Reply-To: <alpine.DEB.2.00.1708111523460.17596@tp.orcam.me.uk>
On 17-08-11 15:31:25, Maciej W. Rozycki wrote:
> On Wed, 9 Aug 2017, Yao Qi wrote:
>
> > > Thanks for your review and testing. I have committed it to master now.
> > > How about the 8.0 branch?
> >
> > Yes, please. Are you able to edit page
> > https://sourceware.org/gdb/wiki/GDB_8.0_Release and add this PR in 8.0.1
> > release? If you don't have the permission to edit, I can do it for you.
>
> I have backported the change now and, after a hiccup, managed to create a
> wiki account. However as you suspected, I seem unable to edit the page as
> it shows as immutable, at least to me. Would you be able to do anything
> about my editing permission? FWIW I have no issues with the sibling GLIBC
> wiki. I'm user `macro' in both wikis.
AFAIK, users on https://sourceware.org/gdb/wiki/EditorGroup have the
permission to edit the wiki. I add `macro' in the list. Does it work?
--
Yao (é½å°§)
next prev parent reply other threads:[~2017-08-11 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 16:36 [PATCH] " Maciej W. Rozycki
2017-08-02 17:53 ` Maciej W. Rozycki
2017-08-04 13:17 ` Simon Marchi
2017-08-04 13:58 ` Maciej W. Rozycki
2017-08-04 13:24 ` Yao Qi
2017-08-04 14:13 ` [PATCH v2] PR breakpoints/21886: " Maciej W. Rozycki
2017-08-07 15:35 ` Yao Qi
2017-08-07 16:05 ` Maciej W. Rozycki
2017-08-09 7:44 ` Yao Qi
2017-08-11 14:31 ` Maciej W. Rozycki
2017-08-11 15:12 ` Yao Qi [this message]
2017-08-11 16:14 ` Maciej W. Rozycki
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=20170811151238.GI8039@1170ee0b50d5 \
--to=qiyaoltc@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@imgtec.com \
--cc=yao.qi@linaro.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