From: Nick Clifton <nickc@redhat.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH V4] gprofng: a new GNU profiler
Date: Wed, 12 Jan 2022 12:42:27 +0000 [thread overview]
Message-ID: <3d87cce5-1ac6-ca35-0baa-576d599acdc7@redhat.com> (raw)
In-Reply-To: <aa6991b2-a3ea-277b-6a56-de598a78017b@oracle.com>
Hi Vladimir,
> I created 4 patches to integrate gprofng into binutils-gdb.
>
> % ls -al 000*
> -rw-rw-r-- 1 vmezents wheel 5901152 Jan 11 12:39 0001-gprofng-add-the-gprofng-tool.patch
> -rw-rw-r-- 1 vmezents wheel 224725 Jan 11 12:39 0002-gprofng-add-testsuite-for-gprofng.patch
> -rw-rw-r-- 1 vmezents wheel 179400 Jan 11 12:39 0003-gprofng-add-the-gprofng-documentation.patch
> -rw-rw-r-- 1 vmezents wheel 26170 Jan 11 12:39 0004-gprofng-add-the-gprofng-build.patch
>
> The first 3 pathes add or change sources only in binutils-gdb.git/gprofng directory.
> 0004-gprofng-add-the-gprofng-build.patch has fixes in Makefile.def and configure.ac to configure the gprofng build.
>
> 0001-gprofng-add-the-gprofng-tool.patch is probably so big to send to binutils@sourceware.org.
>
> I have no permissions to apply pathes.
> What should I do to pushmy fixes for gprofng in binutils-gdb.git ?
Send them to me (or point me at them - they are probably in the email archive somewhere
but I am a little bit swamped at the moment, so anything that you can do to make my life
simpler is a benefit). I strongly suggest that you compress the 0001 patch first though :-)
xz is your friend. Or lzip. Or well pretty much any compression tool...
Cheers
Nick
next prev parent reply other threads:[~2022-01-12 12:43 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 [this message]
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
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=3d87cce5-1ac6-ca35-0baa-576d599acdc7@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--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).