@matheusbsbs / matheus-bagliano / commits / 4a7979ca82
Fork 0

user-manual: document git-show-branch example

Document Junio's show-branch trick for finding out which tags are descendents of a given comit. Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>

J. Bruce Fields committed Jan 29, 2007 at 01:55 UTC 4a7979ca829530c4e5661d553449b0b073a50db3
1 file changed +28 -2
Documentation/user-manual.txt
+28 -2
@@ -933,12 +933,38 @@ actually is an ancestor of v1.5.0-rc1.
933 Alternatively, note that
934
935 -------------------------------------------------
936 -$ git log v1.5.0-rc1..305db0fd
936 +$ git log v1.5.0-rc1..e05db0fd
937 -------------------------------------------------
938
939 -will produce empty output if and only if v1.5.0-rc1 includes 305db0fd,
939 +will produce empty output if and only if v1.5.0-rc1 includes e05db0fd,
940 because it outputs only commits that are not reachable from v1.5.0-rc1.
941
942 +As yet another alternative, the gitlink:git-show-branch[1] command lists
943 +the commits reachable from its arguments with a display on the left-hand
944 +side that indicates which arguments that commit is reachable from. So,
945 +you can run something like
946 +
947 +-------------------------------------------------
948 +$ git show-branch e05db0fd v1.5.0-rc0 v1.5.0-rc1 v1.5.0-rc2
949 +! [e05db0fd] Fix warnings in sha1_file.c - use C99 printf format if
950 +available
951 + ! [v1.5.0-rc0] GIT v1.5.0 preview
952 + ! [v1.5.0-rc1] GIT v1.5.0-rc1
953 + ! [v1.5.0-rc2] GIT v1.5.0-rc2
954 +...
955 +-------------------------------------------------
956 +
957 +then search for a line that looks like
958 +
959 +-------------------------------------------------
960 ++ ++ [e05db0fd] Fix warnings in sha1_file.c - use C99 printf format if
961 +available
962 +-------------------------------------------------
963 +
964 +Which shows that e05db0fd is reachable from itself, from v1.5.0-rc1, and
965 +from v1.5.0-rc2, but not from v1.5.0-rc0.
966 +
967 +
968 Developing with git
969 ===================
970