From: Teemu Likonen <tlikonen@iki.fi>
To: Adam Simpkins <adam@adamsimpkins.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/3] log --graph and rev-list --graph
Date: Tue, 6 May 2008 22:03:05 +0300 [thread overview]
Message-ID: <20080506190305.GA19819@mithlond.arda.local> (raw)
In-Reply-To: <1209897414-10091-1-git-send-email-adam@adamsimpkins.net>
Adam Simpkins wrote (2008-05-04 03:36 -0700):
> This patch series adds a new --graph option to the log and rev-list
> commands. This is pretty much the same code that I sent out in early
> April, but updated to work with the log entry termination fixes in the
> latest master branch.
Looks great, with the exception of the defects we already know: (1)
diff(stat) options write their output to the graph area and (2) --follow
shows really weird lines (gitk has the same "feature").
Other than that it seems really solid. Don't know about the code but
from user's point of view:
Tested-by: Teemu Likonen <tlikonen@iki.fi>
prev parent reply other threads:[~2008-05-06 19:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 10:36 [PATCH 0/3] log --graph and rev-list --graph Adam Simpkins
2008-05-04 10:36 ` [PATCH 1/3] revision API: split parent rewriting and parent printing options Adam Simpkins
2008-05-04 10:36 ` [PATCH 2/3] Add history graph API Adam Simpkins
2008-05-04 10:36 ` [PATCH 3/3] log and rev-list: add --graph option Adam Simpkins
2008-05-05 7:57 ` [PATCH] graph API: eliminate unnecessary indentation Adam Simpkins
2008-05-05 11:38 ` Ping Yin
2008-05-06 6:41 ` [PATCH 3/3] log and rev-list: add --graph option Junio C Hamano
2008-05-06 7:01 ` Adam Simpkins
2008-05-06 6:41 ` [PATCH 2/3] Add history graph API Junio C Hamano
2008-05-04 11:06 ` [PATCH] bash: Add more option completions for 'git log' Teemu Likonen
2008-05-05 2:13 ` [PATCH 0/3] log --graph and rev-list --graph Ping Yin
2008-05-05 6:19 ` Adam Simpkins
2008-05-06 19:03 ` 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=20080506190305.GA19819@mithlond.arda.local \
--to=tlikonen@iki.fi \
--cc=adam@adamsimpkins.net \
--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).