Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: [PATCH] Add git-show-branches-script
Date: Mon, 15 Aug 2005 02:56:06 -0700	[thread overview]
Message-ID: <7v4q9r1q2x.fsf@assigned-by-dhcp.cox.net> (raw)

Often I find myself wanting to do quick branches check when I am
not in the windowing environment and cannot run gitk.

This stupid script shows commits leading to the heads of
interesting branches with indication which ones belong to which
branches, so that fork point is somewhat discernible without
using gitk.

Signed-off-by: Junio C Hamano <junkio@cox.net>
---

 Documentation/git-show-branches-script.txt |   69 ++++++++++++++++++++++++++++
 Documentation/git.txt                      |    2 +
 Makefile                                   |    1 
 git-show-branches-script                   |   53 ++++++++++++++++++++++
 4 files changed, 125 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/git-show-branches-script.txt
 create mode 100755 git-show-branches-script

8d67319c6e28035abdb848b9b2f31a8c5711bd49
diff --git a/Documentation/git-show-branches-script.txt b/Documentation/git-show-branches-script.txt
new file mode 100644
--- /dev/null
+++ b/Documentation/git-show-branches-script.txt
@@ -0,0 +1,69 @@
+git-show-branches-script(1)
+===========================
+v0.99.4, Aug 2005
+
+NAME
+----
+git-show-branches-script - Show branches and their commits.
+
+SYNOPSIS
+--------
+'git show-branches <reference>...'
+
+DESCRIPTION
+-----------
+Shows the head commits from the named <reference> (or all refs under
+$GIT_DIR/refs/heads), and displays concise list of commit logs
+to show their relationship semi-visually.
+
+OPTIONS
+-------
+<reference>::
+	Name of the reference under $GIT_DIR/refs/heads/.
+
+
+OUTPUT
+------
+Given N <references>, the first N lines are the one-line
+description from their commit message.  The branch head that is
+pointed at by $GIT_DIR/HEAD is prefixed with an asterisk '*'
+character while other heads are prefixed with a '!' character.
+
+Following these N lines, one-line log for each commit is
+displayed, indented N places.  If a commit is on the I-th
+branch, the I-th indentation character shows a '+' sign;
+otherwise it shows a space.
+
+The following example shows three branches, "pu", "master" and
+"rc":
+
+	* [pu] Add cheap local clone '-s' flag to git-clone-script
+	 ! [master] Documentation updates.
+	  ! [rc] Merge master into rc
+	+   Add cheap local clone '-s' flag to git-clone-script
+	+   Alternate object pool mechanism updates.
+	+   Audit rev-parse users.
+	++  Documentation updates.
+	  + Merge master into rc
+	+++ [PATCH] plug memory leak in diff.c::diff_free_filepair()
+
+These three branches all forked from a common commit, "[PATCH]
+plug memory leak...", and "rc" has one commit ahead of it.  The
+"master" branch has one different commit that is also shared by
+"pu" branch, and "pu" branch has three more commits on top of
+"master" branch.
+
+
+Author
+------
+Written by Junio C Hamano <junkio@cox.net>
+
+
+Documentation
+--------------
+Documentation by Junio C Hamano.
+
+
+GIT
+---
+Part of the link:git.html[git] suite
diff --git a/Documentation/git.txt b/Documentation/git.txt
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -188,6 +188,8 @@ link:git-pull-script.html[git-pull-scrip
 link:git-commit-script.html[git-commit-script]::
 	Record changes to the repository.
 
+link:git-show-branches-script.html[git-show-branches-script]::
+	Show branches and their commits.
 
 Ancilliary Commands
 -------------------
diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -71,6 +71,7 @@ SCRIPTS=git git-apply-patch-script git-m
 SCRIPTS += git-count-objects-script
 # SCRIPTS += git-send-email-script
 SCRIPTS += git-revert-script
+SCRIPTS += git-show-branches-script
 
 PROG=   git-update-cache git-diff-files git-init-db git-write-tree \
 	git-read-tree git-commit-tree git-cat-file git-fsck-cache \
diff --git a/git-show-branches-script b/git-show-branches-script
new file mode 100755
--- /dev/null
+++ b/git-show-branches-script
@@ -0,0 +1,53 @@
+#!/bin/sh
+#
+# Show refs and their recent commits.
+#
+
+. git-sh-setup-script || die "Not a git repository"
+
+headref=`readlink $GIT_DIR/HEAD`
+case "$#" in
+0)
+	set x `cd $GIT_DIR/refs &&
+	    find heads -type f -print |
+	    sed -e 's|heads/||' |
+	    sort`
+	shift ;;
+esac
+
+hh= in=
+for ref
+do
+	case "/$headref" in
+	*/"$ref") H='*' ;;
+	*) H='!' ;;
+	esac
+	h=`git-rev-parse --verify "$ref^0"` || exit
+	l=`git-log-script --max-count=1 --pretty=oneline "$h" |
+		sed -e 's/^[^ ]* //'`
+	hh="$hh $h"
+	echo "$in$H [$ref] $l"
+	in="$in "
+done
+set x $hh
+shift
+
+git-rev-list --pretty=oneline "$@" |
+while read v l
+do
+	in=''
+	for h
+	do
+		b=`git-merge-base $h $v`
+		case "$b" in
+		$v) in="$in+" ;;
+		*)  in="$in " ;;
+		esac
+	done
+
+	echo "$in $l"
+	case "$in" in
+	*' '*) ;;
+	*) break ;;
+	esac
+done

                 reply	other threads:[~2005-08-15  9:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7v4q9r1q2x.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.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