From: Teemu Likonen <tlikonen@iki.fi>
To: git@vger.kernel.org
Cc: "Stephen Sinclair" <radarsat1@gmail.com>,
"Adam Simpkins" <adam@adamsimpkins.net>
Subject: Re: [PATCH] Add new git-graph command
Date: Tue, 1 Apr 2008 08:07:52 +0300 [thread overview]
Message-ID: <200804010807.52914.tlikonen@iki.fi> (raw)
In-Reply-To: <200804010729.51202.tlikonen@iki.fi>
Teemu Likonen kirjoitti:
> Adam's 'git graph' is a way of viewing log (in terminal environment),
> it looks very similar to 'git log --pretty=oneline' and it accepts
> very much the same command line options. That's why I see 'git log'
> being logical place for such functionality.
>
> Actually, to me it would be more logical if 'git whatchanged' was
> 'git log --changed' or '--verbose / -v' something.
May I add that I'm the kind of user who only understands the porcelain
Git. In my mindset it's best when commands are in logical units by
their functionality (from user's point of view).
I see 'git log' as a command for studying history log and to me 'git
whatchanged' sounds like some user's personal _alias_ to 'git
log --raw --full-history --always' or something (thanks Jeff).
Similarly 'git graph' sounds like an alias to 'git log --pretty=graph'
for someone who uses this a lot.
prev parent reply other threads:[~2008-04-01 5:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 19:58 [PATCH] Add new git-graph command Adam Simpkins
2008-03-30 20:41 ` Jakub Narebski
2008-03-30 22:00 ` Adam Simpkins
2008-03-30 20:44 ` Matthieu Moy
2008-03-30 22:02 ` Adam Simpkins
2008-03-30 22:54 ` Johannes Schindelin
2008-03-30 23:49 ` Junio C Hamano
2008-03-31 7:09 ` Adam Simpkins
2008-03-31 17:17 ` Teemu Likonen
2008-03-31 18:47 ` Adam Simpkins
2008-04-01 4:05 ` Stephen Sinclair
2008-04-01 4:29 ` Teemu Likonen
2008-04-01 5:02 ` Jeff King
2008-04-01 5:07 ` Teemu Likonen [this message]
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=200804010807.52914.tlikonen@iki.fi \
--to=tlikonen@iki.fi \
--cc=adam@adamsimpkins.net \
--cc=git@vger.kernel.org \
--cc=radarsat1@gmail.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