From: Djordje Todorovic <djordje.todorovic@rt-rk.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Ananthakrishna Sowda (asowda)" <asowda@cisco.com>,
"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Latest version of dwarflint?
Date: Tue, 26 Sep 2017 11:39:00 -0000 [thread overview]
Message-ID: <38be3f0d-4fc4-6e75-4f54-cd10bf6360b8@rt-rk.com> (raw)
In-Reply-To: <1506356325.16945.75.camel@klomp.org>
> Do you have patches against the origin/dwarf branch that contained the
>original dwarlint? Or against current master (or the 0.170 release)
>branch?
I have patches that can be applied on top of 0.170 release. I have moved dwarflint and libdw/c++ directories from origin/dwarf branch and then add support in configure and
makefiles to build it successfully. After that I made some fixes and improvements of the utilities.
> If you have them in a git branch and it is easy to extract them
>then using git send-email to this list would probably be easiest. Then
>we can create a new branch as base to apply them on top.
Yes, I have git branch, but these patches are pretty cumulative and I’m breaking up them into more logical pieces, so it would be easier for maintaining. I will be back in a few days.
Thanks,
Djordje
next prev parent reply other threads:[~2017-09-26 11:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 19:47 Ananthakrishna Sowda (asowda)
2017-08-03 9:13 ` Mark Wielaard
2017-09-21 15:59 ` Ananthakrishna Sowda (asowda)
2017-09-21 16:07 ` Djordje Todorovic
2017-09-21 19:00 ` Mark Wielaard
2017-09-22 13:37 ` Djordje Todorovic
2017-09-25 16:18 ` Mark Wielaard
2017-09-26 11:39 ` Djordje Todorovic [this message]
[not found] ` <c2b5f92f-0798-1e43-2095-b282bd5d7879@rt-rk.com>
2017-09-29 12:08 ` Mark Wielaard
2017-09-29 12:26 ` Mark Wielaard
2017-09-29 12:44 ` Djordje Todorovic
2017-09-29 13:07 ` Mark Wielaard
2017-10-06 19:53 ` Mark Wielaard
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=38be3f0d-4fc4-6e75-4f54-cd10bf6360b8@rt-rk.com \
--to=djordje.todorovic@rt-rk.com \
--cc=asowda@cisco.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
/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).