Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: vladimir.mezentsev@oracle.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb passes and returns incorrect values when dealing with small array on Sparc
Date: Tue, 18 Apr 2017 22:20:00 -0000	[thread overview]
Message-ID: <46e1e493-e787-c4c2-e717-3619e5d9f5ee@redhat.com> (raw)
In-Reply-To: <87zifdjti2.fsf@oracle.com>

Hi Jose,

On 04/18/2017 10:28 PM, Jose E. Marchesi wrote:
> 
> Hi Pedro.
> 
>     Sorry for the delay.  I think everyone was hoping that someone
>     that actually groks SPARC stuff would take a look at this.
>     I don't think we have any maintainer currently actively caring for
>     SPARC in particular.  Maybe you guys (Oracle folks) could help
>     review each others' patches?  I think that'd help get these
>     patches in quicker.
> 
> We (the Oracle toolchain team) actually review the GDB patches
> internally from a functional perspective before they are sent upstream.
> 
> We can make it more explicit in our future submissions with a note in
> the patch submission.

Internal review is of course fine and appreciated, but I still think
it better to do at least some of it in the open.  With a bit of visible
involvement, it'll be natural for one (or more) of you guys to
end up being gdb/SPARC maintainer.  (As you know, maintainership
status is individual, not through affiliation.)

Thanks,
Pedro Alves


  reply	other threads:[~2017-04-18 22:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 16:21 vladimir.mezentsev
2017-04-18 14:54 ` Pedro Alves
2017-04-18 21:28   ` Jose E. Marchesi
2017-04-18 22:20     ` Pedro Alves [this message]
2017-04-19  9:01       ` Jose E. Marchesi
     [not found] <1490721669-12560-1-git-send-email-vladimir.mezentsev@oracle.com>
     [not found] ` <5a3397ae-e986-8a36-13ba-ed2cfeb68a12@redhat.com>
2017-03-29 16:38   ` Vladimir Mezentsev
2017-04-18 14:54     ` Pedro Alves
2017-05-16 16:16 vladimir.mezentsev
2017-05-19  9:44 ` Jose E. Marchesi
2017-05-19  9:57   ` Pedro Alves
2017-05-19 10:19     ` Jose E. Marchesi

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=46e1e493-e787-c4c2-e717-3619e5d9f5ee@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jose.marchesi@oracle.com \
    --cc=vladimir.mezentsev@oracle.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