public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: "taylor, david" <david.taylor@emc.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PING] RE: [PATCH v2] Support structure offsets that are 512K bytes or larger.
Date: Tue, 21 Jun 2016 13:20:00 -0000	[thread overview]
Message-ID: <CAH=s-PNaPVN2+iutcOoBOn3fpBVCPScK6OhHU6nAXrDbfhFmag@mail.gmail.com> (raw)
In-Reply-To: <63F1AEE13FAE864586D589C671A6E18B0636DA@MX203CL03.corp.emc.com>

Hi David,

On Tue, Jun 21, 2016 at 1:08 PM, taylor, david <david.taylor@emc.com> wrote:
> The nits you point out are all easy to deal with.  One issue.  You say, in part:
>
>> I rebuild native i686-w64-mingw32 gdb with your patch, the build is
>> OK.  The patch is good to me, some nits below.  You can push it in if no
>> other comments in 3~4 days.
>
> I cannot push it as I do not have 'write after approval' status.

You can fill in this form to request an account on sourceware.org
https://sourceware.org/cgi-bin/pdw/ps_form.cgi

I can sponsor your request, and "email address of person who approved
request" in the form is yao.qi@arm.com

>
> Should I port an updated version addressing the nits?  Or ...?
>

Please post an updated version for the record, and push the patch in once
your account is ready.  If you don't get the account in one week, I can push the
patch in for you.

-- 
Yao (齐尧)

      reply	other threads:[~2016-06-21 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 13:18 taylor, david
2016-06-21  7:56 ` Yao Qi
2016-06-21 12:08   ` taylor, david
2016-06-21 13:20     ` 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='CAH=s-PNaPVN2+iutcOoBOn3fpBVCPScK6OhHU6nAXrDbfhFmag@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=david.taylor@emc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).