From: "Martin Liška" <mliska@suse.cz>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org
Subject: Re: [PATCH V4] gprofng: a new GNU profiler
Date: Mon, 14 Mar 2022 12:12:13 +0100 [thread overview]
Message-ID: <0bf6a37a-65d5-2ea8-140d-6e95fd17a8c5@suse.cz> (raw)
In-Reply-To: <2e79ac0a-4324-b760-2073-fea1ec2333c1@oracle.com>
On 3/9/22 22:13, Vladimir Mezentsev via Binutils wrote:
> Hi Nick,
> I sent you a tar file with patches.
> Could you please apply to the mainline sources.
>
> Thanks to everyone who worked on gprofng.
> Thanks to everyone who helped make gprofng public.
Hello.
Can you please take a look at:
https://sourceware.org/bugzilla/show_bug.cgi?id=28962
Thanks,
Martin
>
> -Vladimir
>
>
>
> On 3/9/22 08:36, Nick Clifton wrote:
>> Hi Vladimir,
>>
>>>> It would be really nice if I could test a built-but-not-installed
>>>> version of the sources....
>>>
>>> Done.
>>>
>>> Please review:
>>> url: https://github.com/oracle/binutils-gdb.git/
>>> branch: oracle/gprofng-v4-2
>>
>> Much better. I think that this branch is ready for merging into
>> the mainline.
>>
>> Not being a git expert, I am going to ask for your advice on this
>> matter. Do you want to merge that branch into the sourceware
>> mainline in a way that preserves your commit history ? If so,
>> is there a git command that can achieve this ? Alternatively do
>> you have a set of patches that I can just apply to the mainline
>> sources ? Or maybe patches for the generic code, plus a blanket
>> import of the gprofng/ directory from the gprofng-v4-2 branch ?
>>
>> Cheers
>> Nick
>>
>>
>
prev parent reply other threads:[~2022-03-14 11:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fcc77804-0d0c-0f8e-5c3b-3ac034340b1a@oracle.com>
2021-11-03 18:05 ` Vladimir Mezentsev
2021-11-15 18:13 ` Ping: " Vladimir Mezentsev
2021-11-29 17:34 ` Vladimir Mezentsev
2021-12-10 9:38 ` Nick Clifton
2021-12-10 17:31 ` Vladimir Mezentsev
2021-12-13 15:13 ` Nick Clifton
2021-12-16 22:22 ` Vladimir Mezentsev
2022-01-12 0:48 ` Vladimir Mezentsev
2022-01-12 12:42 ` Nick Clifton
2022-01-12 15:17 ` Jose E. Marchesi
2022-01-12 15:23 ` Jose E. Marchesi
[not found] ` <c26c71b2-8cf1-2eef-206f-14c4774b2ba0@oracle.com>
2022-01-26 12:04 ` Nick Clifton
2022-01-26 17:10 ` Vladimir Mezentsev
2022-01-27 14:34 ` Jose E. Marchesi
2022-02-02 12:40 ` Maciej W. Rozycki
2022-02-02 16:30 ` Jose E. Marchesi
2022-02-03 6:23 ` Vladimir Mezentsev
2022-02-03 11:02 ` Maciej W. Rozycki
2022-02-03 12:16 ` Jose E. Marchesi
2022-03-02 19:47 ` Vladimir Mezentsev
2022-03-04 13:53 ` Nick Clifton
2022-03-07 21:42 ` Vladimir Mezentsev
2022-03-07 21:57 ` H.J. Lu
2022-03-07 22:25 ` Vladimir Mezentsev
2022-03-09 16:36 ` Nick Clifton
2022-03-09 21:13 ` Vladimir Mezentsev
2022-03-14 11:12 ` Martin Liška [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=0bf6a37a-65d5-2ea8-140d-6e95fd17a8c5@suse.cz \
--to=mliska@suse.cz \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).