Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: "Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>,
	"Achra, Nitika" <Nitika.Achra@amd.com>,
	Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] Fixed gdb to print arrays with very high indexes
Date: Tue, 04 Feb 2020 01:23:00 -0000	[thread overview]
Message-ID: <90a6c389-942b-5a29-970d-dd7300931e5f@simark.ca> (raw)
In-Reply-To: <DM6PR12MB3129B5A33BB11FEC833CB50F9E000@DM6PR12MB3129.namprd12.prod.outlook.com>

On 2020-02-03 12:20 a.m., Sharma, Alok Kumar wrote:
> As I don’t have required permission, It would be great if someone from the gdb-patches pushes this patch?
> 
> Thanks in advance !!
> 
> Regards,
> Alok

Hi Alok,

I'll do that in a few minutes, once I confirms it builds on my machine.

If you plan on contributing patches regularly, it would be an option for you
to get write access to the repo.  You could then push your own patches, once
they are approved.  Let me know if you'd like to do that.

On another note, could you please fix your name in git?  It currently appears
as `alosharm`, which I presume is your username.  You can do either:

  $ git config user.name "Alok Kumar Sharma"

in the binutils-gdb repository, to apply it only to that repo, or:

  $ git config --global user.name "Alok Kumar Sharma"

to apply it to all your repos.

Simon


  reply	other threads:[~2020-02-04  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  5:20 Sharma, Alok Kumar
2020-02-04  1:23 ` Simon Marchi [this message]
2020-02-04  7:37   ` Sharma, Alok Kumar
     [not found] <DM6PR12MB312912C12E60E8EB91778B909E050@DM6PR12MB3129.namprd12.prod.outlook.com>
     [not found] ` <DM6PR12MB31298B64316E8F9E578EE9F79E050@DM6PR12MB3129.namprd12.prod.outlook.com>
2020-01-31 10:28   ` Tom Tromey
2020-02-02 16:06     ` Sharma, Alok Kumar

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=90a6c389-942b-5a29-970d-dd7300931e5f@simark.ca \
    --to=simark@simark.ca \
    --cc=AlokKumar.Sharma@amd.com \
    --cc=JiniSusan.George@amd.com \
    --cc=Nitika.Achra@amd.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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