public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] PR28972, gprofng libraries should be installed under $(pkglibdir)
Date: Mon, 21 Mar 2022 08:48:05 -0700	[thread overview]
Message-ID: <f6e5e357-0234-0b60-dcbc-d72630c1eadd@oracle.com> (raw)
In-Reply-To: <CAMe9rOrD93s=8QLT-JOfhvNA61E5Cynj12E-Z2Yc+eEJEJvZRQ@mail.gmail.com>



On 3/20/22 16:09, H.J. Lu wrote:
> On Thu, Mar 17, 2022 at 10:01 AM Vladimir Mezentsev via Binutils
> <binutils@sourceware.org>  wrote:
>> From: Vladimir Mezentsev<vladimir.mezentsev@oracle.com>
>>
>> gprofng/ChangeLog
>> 2022-03-17  Vladimir Mezentsev<vladimir.mezentsev@oracle.com>
>>
> Please add PR gprofng/28972 here so that
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=28972
>
> will be updated when this patch is checked in.   Since you are the
> gprofng owner,
> you don't need extra approval to check in your bug fix.
>
>

  Hi HJ,
I need permissions to check in.
How can I get this?

Thank you,
-Vladimir

  parent reply	other threads:[~2022-03-21 15:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 17:00 vladimir.mezentsev
2022-03-20 23:09 ` H.J. Lu
2022-03-20 23:45   ` H.J. Lu
2022-03-21  1:29     ` H.J. Lu
2022-03-21 15:48   ` Vladimir Mezentsev [this message]
2022-03-21 19:02     ` H.J. Lu
2022-03-21 20:51       ` Vladimir Mezentsev
2022-03-21 21:05         ` H.J. Lu
2022-03-21 21:15           ` Vladimir Mezentsev
2022-03-21 21:49             ` H.J. Lu
     [not found]               ` <d585b1f8-f3d0-7a0c-ef9f-1dcaff9c7307@oracle.com>
2022-03-22  2:42                 ` H.J. Lu
2022-03-22  4:56                   ` Vladimir Mezentsev
2022-03-22 19:04               ` Vladimir Mezentsev

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=f6e5e357-0234-0b60-dcbc-d72630c1eadd@oracle.com \
    --to=vladimir.mezentsev@oracle.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.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).