From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Yao Qi <qiyaoltc@gmail.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 16:14:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1708111707000.17596@tp.orcam.me.uk> (raw)
In-Reply-To: <20170811151238.GI8039@1170ee0b50d5>
On Fri, 11 Aug 2017, Yao Qi wrote:
> > 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?
It does, thank you! Page updated.
BTW, PR 21555 still has to be closed it would seem. I'm not sure if it's
bugzilla or my browser (or myself), but I had troubles closing PR 21886 as
well, as the intended status flipped from RESOLVED to WAITING as I was
typing in the comment.
Maciej
prev parent reply other threads:[~2017-08-11 16:14 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
2017-08-11 16:14 ` Maciej W. Rozycki [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=alpine.DEB.2.00.1708111707000.17596@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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