From: Arnaldo Carvalho de Melo <acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Ilpo Järvinen" <ilpo.jarvinen-pxSi+dnQzZMxHbG02/KK1g@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: diff vs codiff against empty
Date: Thu, 31 Jan 2008 10:08:01 -0200 [thread overview]
Message-ID: <20080131120801.GI1819@ghostprotocols.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801302133380.5832-Y/UOj9v5BLQhZigby9b+C6cUovnZ0M2TMR2xtNvyitY@public.gmane.org>
Em Wed, Jan 30, 2008 at 09:42:18PM +0200, Ilpo Järvinen escreveu:
> Hi,
>
> Not a bad problem but makes some tricks I do harder than they would need
> to be:
>
> ijjarvin@kivilampi-30:~/work/src/submit$ diff /dev/null lib/jhash.o
> Binary files /dev/null and lib/jhash.o differ
> ijjarvin@kivilampi-30:~/work/src/submit$ codiff /dev/null lib/jhash.o
> codiff: /dev/null: not a valid ELF file
[acme@doppio examples]$ codiff /dev/null hello
hello.c:
main | +47
1 function changed, 47 bytes added, diff: +47
[acme@doppio examples]$ codiff hello /dev/null
hello.c:
main | -47
1 function changed, 47 bytes removed, diff: -47
[acme@doppio examples]$
> I.e., I created new file jhash and just want to diff it against empty. I
> also tried codiff against echo "" | gcc -g -c -o lib/jhash.o.base -x c -
> but that wasn't any better. I can fix that with sed trick by using pfunct
> -s for it first though.
>
> Btw, codiffs help/usage printout is incorrect or uses unusual notation, it
> uses [] brackets around old_file and new_file even though they are not
> optional arguments.
Fixed in all the dwarves, thanks.
- Arnaldo
parent reply other threads:[~2008-01-31 12:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.64.0801302133380.5832-Y/UOj9v5BLQhZigby9b+C6cUovnZ0M2TMR2xtNvyitY@public.gmane.org>]
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=20080131120801.GI1819@ghostprotocols.net \
--to=acme-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ilpo.jarvinen-pxSi+dnQzZMxHbG02/KK1g@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 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 NNTP newsgroup(s).