From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git log [diff-tree options]...
Date: Sun, 09 Apr 2006 11:46:56 -0700 [thread overview]
Message-ID: <7vbqvabn8f.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.64.0604090950590.9504@g5.osdl.org
Linus Torvalds <torvalds@osdl.org> writes:
> I wonder... This all looks fine, but there are actually two different
> "diffs" that can be shown for "git log --diff <pathlimiter>":
>
> - the whole diff for a commit
> - the path-limited diff
Yes, exactly the same way sometimes you would want just pickaxe,
sometimes you would want it with --pickaxe-all.
Also, I might have to rethink --max-count logic -- I think it is
reasonable to skip the commit when doing limiting by diff like
"whatchanged" does, but one thing I find suboptimal with the
current whatchanged is that it does not count commits that are
actually shown (it counts what the upstream rev-list feeds
diff-tree). With the "git log --diff" based whatchanged, it
becomes trivial to skip the revs->max_count limiting and have
the caller count the commits it actually does something
user-visible to, instead of counting the commits it pulled out
of get_revision().
BTW I think I could remove the log message generation part of
"git log" and have it use the one in log-tree (which I will
probably rewrite not to format the message into the static
this_header[] buffer when it is not shown).
Another thing that might be useful is to teach diff-* to do the
diffstat part internally. After that is in place we could
introduce --pretty=patch to have "git log" produce format-patch
compatible output.
next prev parent reply other threads:[~2006-04-09 18:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 9:04 [PATCH] git log [diff-tree options] Junio C Hamano
2006-04-09 9:16 ` Junio C Hamano
2006-04-09 16:53 ` Linus Torvalds
2006-04-09 18:46 ` Junio C Hamano [this message]
2006-04-09 19:02 ` Linus Torvalds
2006-04-09 19:08 ` Junio C Hamano
2006-04-09 19:26 ` Linus Torvalds
2006-04-09 21:13 ` Johannes Schindelin
2006-04-09 22:01 ` Johannes Schindelin
2006-04-09 22:22 ` Timo Hirvonen
2006-04-10 8:10 ` Johannes Schindelin
2006-04-09 23:51 ` Junio C Hamano
2006-04-10 0:06 ` Linus Torvalds
2006-04-10 8:22 ` Johannes Schindelin
2006-04-11 0:04 ` Randal L. Schwartz
2006-04-11 0:12 ` Junio C Hamano
2006-04-11 0:31 ` Petr Baudis
2006-04-11 0:50 ` Randal L. Schwartz
2006-04-10 23:42 ` Junio C Hamano
2006-04-10 23:43 ` [PATCH] tree-diff: do not assume we use only one pathspec Junio C Hamano
2006-04-10 23:44 ` [PATCH] git log --full-diff Junio C Hamano
2006-04-10 23:54 ` [PATCH] git log [diff-tree options] Linus Torvalds
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=7vbqvabn8f.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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.