From: Julian Seward <jseward@acm.org>
To: overseers@sourceware.org, Andreas Arnez <arnez@linux.ibm.com>
Cc: Mark Wielaard <mark@klomp.org>
Subject: Re: Commit access for Andreas Arnez?
Date: Mon, 24 Sep 2018 07:52:00 -0000 [thread overview]
Message-ID: <07385bbd-6b6f-39fe-f752-0f595d996180@acm.org> (raw)
In-Reply-To: <20180922094742.GD8144@wildebeest.org>
Hi Mark, [Sourceware overseers, please see second para]
Yes, I would prefer that we get as many s390 fixes in before release
as possible. I would be happy to hold the release until the end of the week.
Sourceware overseers: please add Andreas Arnez as a committer for Valgrind.
I approve. I am CCing Andreas on this message. Andreas, please can you also
send a message to overseers@sourceware.org, ccing Mark and me, to say you're
OK with this?
Thank you, all.
J
On 22/09/18 11:47, Mark Wielaard wrote:
> Hi Julian,
>
> I have been testing some of the patches by Andreas.
> He already has commit access to other projects like gdb
> on sourceware. Maybe he also should have commit access
> for valgrind?
>
> If so, he should sent an email to overseers@sourceware.org
> requesting to be added to the valgrind group, CCing you,
> and stating you approve.
>
> The patch for Bug 396839
> s390x: Trap instructions not implemented
> Looks good to me.
>
> The patches for Bug 385409
> s390x: z13 vector integer instructions not implemented
> Done together with Vadim Barkov could be cleaned up
> so it is implemented correctly immediately instead of
> patches on top of patches. IMHO.
>
> These patches seem close to completion, so I wouldn't mind if
> the release waits for them. But that is really up to you, there
> is always some reason to delay :)
>
> Cheers,
>
> Mark
>
next parent reply other threads:[~2018-09-24 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180922094742.GD8144@wildebeest.org>
2018-09-24 7:52 ` Julian Seward [this message]
2018-09-24 13:17 ` Ian Lance Taylor
2018-09-24 13:30 ` Julian Seward
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=07385bbd-6b6f-39fe-f752-0f595d996180@acm.org \
--to=jseward@acm.org \
--cc=arnez@linux.ibm.com \
--cc=mark@klomp.org \
--cc=overseers@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).