From: Jeff King <peff@peff.net>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: Stephen Sinclair <radarsat1@gmail.com>,
git@vger.kernel.org, Adam Simpkins <adam@adamsimpkins.net>
Subject: Re: [PATCH] Add new git-graph command
Date: Tue, 1 Apr 2008 01:02:29 -0400 [thread overview]
Message-ID: <20080401050229.GA23876@coredump.intra.peff.net> (raw)
In-Reply-To: <200804010729.51202.tlikonen@iki.fi>
On Tue, Apr 01, 2008 at 07:29:51AM +0300, Teemu Likonen wrote:
> 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.
Adam suggested that it may be possible to abstract the graphing API so
that it can be called progressively. I would love to see:
git log --pretty=format:'%g %h %s'
where %g would be "the graph lines for this commit." But maybe that is
not workable since the graph may take multiple lines to show.
> Actually, to me it would be more logical if 'git whatchanged' was 'git
> log --changed' or '--verbose / -v' something.
How about:
git log --raw --full-history --always
which is identical. Though in most cases, one would be happy with "git
log --raw". I think whatchanged really only exists separately because it
predates the merging of many of the revision-walking commands.
-Peff
next prev parent reply other threads:[~2008-04-01 5:03 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 [this message]
2008-04-01 5:07 ` Teemu Likonen
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=20080401050229.GA23876@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=adam@adamsimpkins.net \
--cc=git@vger.kernel.org \
--cc=radarsat1@gmail.com \
--cc=tlikonen@iki.fi \
/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