From: Junio C Hamano <gitster@pobox•com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail•com>
Cc: Git <git@vger•kernel.org>, Christian Couder <christian.couder@gmail•com>
Subject: Re: Is there a --stat or --numstat like option that'll allow me to have my cake and eat it too?
Date: Tue, 08 Mar 2016 09:40:46 -0800 [thread overview]
Message-ID: <xmqqoaaolvfl.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CACBZZX7o+VA1RVvja3xtBQf+rr2bWoByas4D5GKZ_VfQr7H19w@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue, 8 Mar 2016 16:08:21 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail•com> writes:
> What I really want is something for git-log more like
> git-for-each-ref, so I could emit the following info for each file
> being modified delimited by some binary marker:
>
> - file name before
> - file name after
> - is rename?
> - is binary?
> - size in bytes before
> - size it bytes after
> - removed lines
> - added lines
>
> I think no combination of git-log options or any built-in machinery
> comes close to giving me all of that without having to do multiple
> passes with some combination of git-log and git-show, but I'd love to
> be proven wrong.
I do not think such a thing exists. From the look of the above
list, if I were implementing it, I'd think it would be the easiest
if it is built as a new output format of "diff" that sits next to
existing --stat, --patch, and --numstat formats, i.e. you would be
writing a new aevars_stat_consume() callback function and calling
xdi_diff_outf() like everybody else. A possible output format may
look as if we are showing "log --patch" output with a bit more
extended diff header lines (e.g. in addition to "rename from", etc.,
you would have "bytes before" and other new types of headers), but
without the actual patch text.
next prev parent reply other threads:[~2016-03-08 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 15:08 Is there a --stat or --numstat like option that'll allow me to have my cake and eat it too? Ævar Arnfjörð Bjarmason
2016-03-08 17:40 ` Junio C Hamano [this message]
2016-03-08 20:51 ` Jeff King
2016-03-08 20:58 ` Ævar Arnfjörð Bjarmason
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=xmqqoaaolvfl.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=avarab@gmail$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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