From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Tentative built-in "git show"
Date: Sat, 15 Apr 2006 12:28:06 -0700 [thread overview]
Message-ID: <7v3bgefxkp.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604151203060.3701@g5.osdl.org> (Linus Torvalds's message of "Sat, 15 Apr 2006 12:09:56 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> This uses the "--no-walk" flag that I never actually implemented (but I'm
> sure I mentioned it) to make "git show" be essentially the same thing as
> "git whatchanged --no-walk".
I sometimes do "git show -4" myself, and wondered why defaulting
to "-n 1"is insufficient, but if you do something like this to
check the tip of each branch:
git show master next pu
this may make sense.
Otherwise, it feels to me that (I haven't had caffeine nor
nicotine yet, so I need to re-think this later) log, show and
whatchanged are the same program in disguise with different set
of defaults.
log --pretty
show --pretty -n1 -p
whatchanged --pretty -r
... which implies that some of them might become historical
curiosity and no real reason to teach about each of them in the
tutorial.
next prev parent reply other threads:[~2006-04-15 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 19:09 Tentative built-in "git show" Linus Torvalds
2006-04-15 19:28 ` Junio C Hamano [this message]
2006-04-15 20:57 ` 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=7v3bgefxkp.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 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).