From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Oct 2009, #02; Sun, 11)
Date: Wed, 14 Oct 2009 20:29:20 +0200 [thread overview]
Message-ID: <4AD61880.4040600@web.de> (raw)
In-Reply-To: <7vfx9pmhae.fsf@alter.siamese.dyndns.org>
Junio C Hamano schrieb:
> * js/diff-verbose-submodule (2009-10-04) 1 commit.
> - Add the --submodule-summary option to the diff option family
>
> Dscho sounded like he has some corrections after list comments, but I did
> not pick up his interdiff in the middle.
Dscho condensed his initial patch with the interdiff you mentioned,
additionally silenced a compiler warning and activated --first-parent.
This follows as patch 1/4. Patches 2/4 to 4/4 contain my two bugfixes
and the testcase i copied from submodule summary while adapting it to
the changes of the output format.
The remaining differences from the output shown by submodule summary are:
1) git diff shows only two dots for a fast forward (submodule summary
always shows three)
2) git diff shows "Submodule" instead of a single '*' in the first line
3) git diff doesn't add a newline after each shortlog
4) submodule summary prints out the number of shortlog entries, this
version does not
5) submodule summary can limit the number of shortlog lines, git diff
can't do that right now
6) When files are replaced by a submodules or vice versa, git diff
generates an extra hunk for the deleted/added file and one saying
"(new submodule)"/"(submodule deleted)"
> The output format needs to be described better here and also in
> Documentation/diff-format.txt.
Will do when it is clear which of the 6 differences should be fixed and
which can stay.
Jens Lehmann (3):
fix indentation depth for git diff --submodule-summary
fix output for deleted submodules in git diff --submodule-summary
add tests for git diff --submodule-summary
Johannes Schindelin (1):
Add the --submodule-summary option to the diff option family
Documentation/diff-options.txt | 4 +
Makefile | 2 +
diff.c | 14 +++
diff.h | 3 +
submodule.c | 113 ++++++++++++++++++++
submodule.h | 8 ++
t/t4041-diff-submodule-summary.sh | 206 +++++++++++++++++++++++++++++++++++++
7 files changed, 350 insertions(+), 0 deletions(-)
create mode 100644 submodule.c
create mode 100644 submodule.h
create mode 100755 t/t4041-diff-submodule-summary.sh
next prev parent reply other threads:[~2009-10-14 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 3:18 What's cooking in git.git (Oct 2009, #02; Sun, 11) Junio C Hamano
2009-10-12 5:14 ` Jeff King
2009-10-12 22:52 ` Junio C Hamano
2009-10-14 4:24 ` Jeff King
2009-10-12 6:23 ` Sverre Rabbelier
2009-10-14 18:29 ` Jens Lehmann [this message]
2009-10-14 18:30 ` [PATCH 1/4] Add the --submodule-summary option to the diff option family Jens Lehmann
2009-10-14 18:31 ` [PATCH 2/4] fix indentation depth for git diff --submodule-summary Jens Lehmann
2009-10-14 18:31 ` [PATCH 3/4] fix output for deleted submodules in " Jens Lehmann
2009-10-14 18:32 ` [PATCH 4/4] add tests for " Jens Lehmann
2009-10-14 20:34 ` submodule-summary Junio C Hamano
2009-10-14 21:27 ` submodule-summary Jens Lehmann
2009-10-14 22:42 ` submodule-summary Junio C Hamano
2009-10-15 10:34 ` submodule-summary Jens Lehmann
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=4AD61880.4040600@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).