From: "Wiederhake, Tim" <tim.wiederhake@intel.com>
To: Pedro Alves <palves@redhat.com>,
"Metzger, Markus T" <markus.t.metzger@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v4 0/1] btrace: Resume recording after disconnect.
Date: Fri, 22 Jul 2016 12:54:00 -0000 [thread overview]
Message-ID: <9676A094AF46E14E8265E7A3F4CCE9AF8CDB25@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <d100ea6c-a9d4-7d00-ac9a-638f401f537e@redhat.com>
Thanks!
I just submitted the request.
- Tim
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Friday, July 22, 2016 2:43 PM
> To: Metzger, Markus T <markus.t.metzger@intel.com>; Wiederhake, Tim
> <tim.wiederhake@intel.com>; gdb-patches@sourceware.org
> Subject: Re: [PATCH v4 0/1] btrace: Resume recording after disconnect.
>
> On 07/22/2016 01:40 PM, Metzger, Markus T wrote:
>
> > AFAIK Tim does not yet have write-access to the GDB repo. Do you maybe
> > know where he can apply for it?
>
> https://sourceware.org/ -> "I need an account on sourceware for
> git/svn/cvs write access to project XYZ?"
>
> Feel free to list me as sponsor.
>
> Thanks,
> Pedro Alves
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2016-07-22 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 11:15 Tim Wiederhake
2016-07-22 11:15 ` [PATCH v4 1/1] " Tim Wiederhake
2016-07-22 11:42 ` [PATCH v4 0/1] " Pedro Alves
2016-07-22 12:40 ` Metzger, Markus T
2016-07-22 12:42 ` Pedro Alves
2016-07-22 12:54 ` Wiederhake, Tim [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=9676A094AF46E14E8265E7A3F4CCE9AF8CDB25@irsmsx105.ger.corp.intel.com \
--to=tim.wiederhake@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).