All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Diego 'Flameeyes' Pettenò"
	<flameeyes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Feature request: codiff only considering file basename
Date: Fri, 24 Oct 2008 11:19:25 -0200	[thread overview]
Message-ID: <20081024131925.GC15444@ghostprotocols.net> (raw)
In-Reply-To: <m27i7yxhk5.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Em Fri, Oct 24, 2008 at 03:12:58PM +0200, Diego 'Flameeyes' Pettenò escreveu:
> 
> I found myself today in the situation of using codiff on two binaries
> built with the same sources, but reorganised around; since I noticed a
> non-zero difference on codiff, I would have liked to know where the
> difference would be, but since the source files' path has changed,
> codiff is showing me too much noise and I can't figure out what changed.
> 
> Optionally considering the basename of the source files would be very
> nice way to reduce the noise and only show the important data.

Can you show an excerpt of the output you would like to see changed?
 
> Thanks!
> 
> P.S.: is a new release to be expected? Or git is going to be the only
> way?

I was expecting to make a release with the CTF encoder, but will try and
get one out RSN with what is in git.

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe dwarves" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-10-24 13:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 13:12 Feature request: codiff only considering file basename Diego 'Flameeyes' Pettenò
     [not found] ` <m27i7yxhk5.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-10-24 13:19   ` Arnaldo Carvalho de Melo [this message]
2008-11-09 19:17     ` Diego 'Flameeyes' Pettenò

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=20081024131925.GC15444@ghostprotocols.net \
    --to=acme-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=flameeyes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.