From: Yao Qi <yao@codesourcery.com>
To: ali_anwar <ali_anwar@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: "maint print arch" causing gdb crash
Date: Mon, 08 Oct 2012 13:12:00 -0000 [thread overview]
Message-ID: <5072D120.7030800@codesourcery.com> (raw)
In-Reply-To: <5072BCA5.7020001@codesourcery.com>
On 10/08/2012 07:44 PM, ali_anwar wrote:
The changelog looks good to me. Thanks.
> Thanks Yao. Please find attached the updated patch. Please also note
> that its my first patch for gdb. I might not have the commit rights.
> What you suggest should I do under such circumstances?
Mentor has a corporate assignment, so you don't have to do that. What
you need is a sourceware account. With that account, you can commit
this patch by yourself. You can submit your account request here,
http://sourceware.org/cgi-bin/pdw/ps_form.cgi
In that form, you'll fill in the mail address of people who approve your
access. Maybe Stan can approve your access, because he approved this
patch. :)
--
Yao
prev parent reply other threads:[~2012-10-08 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 14:15 ali_anwar
2012-10-05 22:05 ` Stan Shebs
2012-10-07 9:07 ` Yao Qi
2012-10-08 11:47 ` ali_anwar
2012-10-08 13:12 ` Yao Qi [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=5072D120.7030800@codesourcery.com \
--to=yao@codesourcery.com \
--cc=ali_anwar@codesourcery.com \
--cc=gdb-patches@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