From: Jan Engelhardt <jengelh@computergmbh.de>
To: git@vger.kernel.org
Cc: jnareb@gmail.com, kzak@redhat.com
Subject: [announce+patch] git-forest 20080402
Date: Wed, 2 Apr 2008 22:58:14 +0200 [thread overview]
Message-ID: <1207169895-25949-1-git-send-email-jengelh@computergmbh.de> (raw)
Hi,
here is the current snapshot of git-forest, a text-based tree
visualizer, as a patch to the git.git/contrib/ directory.
What's new since the last posting is that it now displays [HEAD]
along with a commit, since HEAD does not always need to be the
first commit that is graphed.
The --all option now includes graphing a detached HEAD, as can
happen on switching to a non-branch and during rebases.
Speaking of rebases, git-forest will now also show where you are in
a rebase operation -- quite handy if you forget whether you actually are
in one (happened to me time and again and when you finally notice, you
need to play with HEAD@{x} to restore it) -- it can be suppressed
with --no-rebase.
I updated the screenshot at
http://jengelh.hopto.org/images/git-forest.png (URL unchanged).
Color-agnostic people may use the --no-color option. (Tag colors
follow gitk as far as the 16 colors permit.)
The direct grab URL for the script is still
http://dev.computergmbh.de/gitweb.cgi?p=hxtools;a=blob_plain;f=bin/git-forest
but of course a patch is provided below with the intent of getting it
into contrib/ at least.
thanks,
Jan
N.B.: This was a ridiculous command to get it right...
can't this be done easier?
`git-format-patch -C -M --stat=72 --summary -p --thread -n HEAD^..HEAD &&
git-send-email --suppress-from --no-chain --compose --to git@xxx 00*`
next reply other threads:[~2008-04-02 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 20:58 Jan Engelhardt [this message]
2008-04-02 20:58 ` [PATCH 1/1] Import git-forest Jan Engelhardt
2008-04-02 21:49 ` Junio C Hamano
2008-04-03 7:27 ` [PATCH] Import git-forest (20080403) Jan Engelhardt
2008-04-03 8:39 ` Junio C Hamano
2008-04-03 9:03 ` Jan Engelhardt
2008-04-03 10:03 ` Jeff King
2008-04-03 10:14 ` [announce+patch] git-forest 20080402 Jeff King
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=1207169895-25949-1-git-send-email-jengelh@computergmbh.de \
--to=jengelh@computergmbh.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=kzak@redhat.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).