From 9dcc829fe13b7c843a1df6c38479d5b8b8c7d20f Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Fri, 16 Sep 2005 22:30:55 -0700 Subject: Retire rev-tree. Some old scripts might still use git-rev-tree, but it really is clearly inferior in every way to git-rev-list that such scripts should be fixed anyway. Fixing them should be pretty easy. Signed-off-by: Junio C Hamano --- Documentation/git-rev-tree.txt | 88 ---------------------------- Documentation/git.txt | 3 - Documentation/howto/using-topic-branches.txt | 4 +- 3 files changed, 2 insertions(+), 93 deletions(-) delete mode 100644 Documentation/git-rev-tree.txt (limited to 'Documentation') diff --git a/Documentation/git-rev-tree.txt b/Documentation/git-rev-tree.txt deleted file mode 100644 index aa98f64b94..0000000000 --- a/Documentation/git-rev-tree.txt +++ /dev/null @@ -1,88 +0,0 @@ -git-rev-tree(1) -=============== -v0.1, May 2005 - -NAME ----- -git-rev-tree - Provides the revision tree for one or more commits - - -SYNOPSIS --------- -'git-rev-tree' [--edges] [--cache ] [^] [[^]] - -DESCRIPTION ------------ -Provides the revision tree for one or more commits. - -OPTIONS -------- ---edges:: - Show edges (ie places where the marking changes between parent - and child) - ---cache :: - Use the specified file as a cache from a previous git-rev-list run - to speed things up. Note that this "cache" is totally different - concept from the directory index. Also this option is not - implemented yet. - -[^]:: - The commit id to trace (a leading caret means to ignore this - commit-id and below) - -Output ------- - - : [: ]\* - -:: - Date in 'seconds since epoch' - -:: - id of commit object - -:: - id of each parent commit object (>1 indicates a merge) - -:: - - The flags are read as a bitmask representing each commit - provided on the commandline. eg: given the command: - - $ git-rev-tree - - The output: - - :5 - - means that is reachable from (1) and (4) - -A revtree can get quite large. "git-rev-tree" will eventually allow -you to cache previous state so that you don't have to follow the whole -thing down. - -So the change difference between two commits is literally - - git-rev-tree [commit-id1] > commit1-revtree - git-rev-tree [commit-id2] > commit2-revtree - join -t : commit1-revtree commit2-revtree > common-revisions - -(this is also how to find the most common parent - you'd look at just -the head revisions - the ones that aren't referred to by other -revisions - in "common-revision", and figure out the best one. I -think.) - - -Author ------- -Written by Linus Torvalds - -Documentation --------------- -Documentation by David Greaves, Junio C Hamano and the git-list . - -GIT ---- -Part of the gitlink:git[7] suite - diff --git a/Documentation/git.txt b/Documentation/git.txt index e9158895b1..2684fa9393 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -134,9 +134,6 @@ gitlink:git-merge-base[1]:: gitlink:git-rev-list[1]:: Lists commit objects in reverse chronological order -gitlink:git-rev-tree[1]:: - Provides the revision tree for one or more commits - gitlink:git-show-index[1]:: Displays contents of a pack idx file. diff --git a/Documentation/howto/using-topic-branches.txt b/Documentation/howto/using-topic-branches.txt index b3b4d2c97a..d30fa85048 100644 --- a/Documentation/howto/using-topic-branches.txt +++ b/Documentation/howto/using-topic-branches.txt @@ -245,7 +245,7 @@ gb=$(tput setab 2) rb=$(tput setab 1) restore=$(tput setab 9) -if [ `git-rev-tree release ^test | wc -c` -gt 0 ] +if [ `git-rev-list release ^test | wc -c` -gt 0 ] then echo $rb Warning: commits in release that are not in test $restore git-whatchanged release ^test @@ -262,7 +262,7 @@ do status= for ref in test release linus do - if [ `git-rev-tree $branch ^$ref | wc -c` -gt 0 ] + if [ `git-rev-list $branch ^$ref | wc -c` -gt 0 ] then status=$status${ref:0:1} fi -- cgit v1.2.1