{"thread":{"id":"6418","subject":"[PATCH 2/2] Refer users to git-rev-parse for revision specification syntax.","startedAt":"2007-01-18T02:08:09Z","lastAt":"2007-01-18T02:08:09Z","messageCount":1,"participants":["Shawn O. Pearce"],"isPatch":true,"patchVersion":1,"patchTotal":2},"messages":[{"id":"31940","messageId":"20070118020809.GB23488@spearce.org","threadId":"6418","inReplyTo":"834ec15f66b9f03b36643cac1c924dcf9bf92f41.1169086075.git.spearce@spearce.org","subject":"[PATCH 2/2] Refer users to git-rev-parse for revision specification syntax.","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-01-18T02:08:09Z","receivedAt":"2007-01-18T02:08:09Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"The revision specification syntax (sometimes referred to as\nSHA1-expressions) is accepted almost everywhere in Git by\nalmost every tool.  Unfortunately it is only documented in\ngit-rev-parse.txt, and most users don't know to look there.\n\nSigned-off-by: Shawn O. Pearce <spearce@spearce.org>\n---\n Documentation/git-cherry-pick.txt  |    2 ++\n Documentation/git-diff.txt         |    3 +++\n Documentation/git-format-patch.txt |    4 +++-\n Documentation/git-log.txt          |    3 +++\n Documentation/git-revert.txt       |    2 ++\n Documentation/git-show.txt         |    2 ++\n Documentation/gitk.txt             |    2 ++\n 7 files changed, 17 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt\nindex 875edb6..3149d08 100644\n--- a/Documentation/git-cherry-pick.txt\n+++ b/Documentation/git-cherry-pick.txt\n@@ -19,6 +19,8 @@ OPTIONS\n -------\n <commit>::\n \tCommit to cherry-pick.\n+\tFor a more complete list of ways to spell commits, see\n+\t\"SPECIFYING REVISIONS\" section in gitlink:git-rev-parse[1].\n \n -e|--edit::\n \tWith this option, `git-cherry-pick` will let you edit the commit\ndiff --git a/Documentation/git-diff.txt b/Documentation/git-diff.txt\nindex 8977877..6a098df 100644\n--- a/Documentation/git-diff.txt\n+++ b/Documentation/git-diff.txt\n@@ -47,6 +47,9 @@ Just in case if you are doing something exotic, it should be\n noted that all of the <commit> in the above description can be\n any <tree-ish>.\n \n+For a more complete list of ways to spell <commit>, see\n+\"SPECIFYING REVISIONS\" section in gitlink:git-rev-parse[1].\n+\n \n OPTIONS\n -------\ndiff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt\nindex 23acb47..574cf76 100644\n--- a/Documentation/git-format-patch.txt\n+++ b/Documentation/git-format-patch.txt\n@@ -20,7 +20,9 @@ DESCRIPTION\n Prepare each commit between <since> and <until> with its patch in\n one file per commit, formatted to resemble UNIX mailbox format.\n If ..<until> is not specified, the head of the current working\n-tree is implied.\n+tree is implied.  For a more complete list of ways to spell\n+<since> and <until>, see \"SPECIFYING REVISIONS\" section in\n+gitlink:git-rev-parse[1].\n \n The output of this command is convenient for e-mail submission or\n for use with gitlink:git-am[1].\ndiff --git a/Documentation/git-log.txt b/Documentation/git-log.txt\nindex 60610f9..b802946 100644\n--- a/Documentation/git-log.txt\n+++ b/Documentation/git-log.txt\n@@ -34,6 +34,9 @@ include::pretty-formats.txt[]\n \tShow only commits between the named two commits.  When\n \teither <since> or <until> is omitted, it defaults to\n \t`HEAD`, i.e. the tip of the current branch.\n+\tFor a more complete list of ways to spell <since>\n+\tand <until>, see \"SPECIFYING REVISIONS\" section in\n+\tgitlink:git-rev-parse[1].\n \n -p::\n \tShow the change the commit introduces in a patch form.\ndiff --git a/Documentation/git-revert.txt b/Documentation/git-revert.txt\nindex 71f7815..8081bba 100644\n--- a/Documentation/git-revert.txt\n+++ b/Documentation/git-revert.txt\n@@ -19,6 +19,8 @@ OPTIONS\n -------\n <commit>::\n \tCommit to revert.\n+\tFor a more complete list of ways to spell commit names, see\n+\t\"SPECIFYING REVISIONS\" section in gitlink:git-rev-parse[1].\n \n -e|--edit::\n \tWith this option, `git-revert` will let you edit the commit\ndiff --git a/Documentation/git-show.txt b/Documentation/git-show.txt\nindex c210b9a..9051951 100644\n--- a/Documentation/git-show.txt\n+++ b/Documentation/git-show.txt\n@@ -32,6 +32,8 @@ OPTIONS\n -------\n <object>::\n \tThe name of the object to show.\n+\tFor a more complete list of ways to spell object names, see\n+\t\"SPECIFYING REVISIONS\" section in gitlink:git-rev-parse[1].\n \n include::pretty-formats.txt[]\n \ndiff --git a/Documentation/gitk.txt b/Documentation/gitk.txt\nindex f1aeb07..6e2a878 100644\n--- a/Documentation/gitk.txt\n+++ b/Documentation/gitk.txt\n@@ -47,6 +47,8 @@ frequently used options.\n \tmeaning show from the given revision and back, or it can be a range in\n \tthe form \"'<from>'..'<to>'\" to show all revisions between '<from>' and\n \tback to '<to>'. Note, more advanced revision selection can be applied.\n+\tFor a more complete list of ways to spell object names, see\n+\t\"SPECIFYING REVISIONS\" section in gitlink:git-rev-parse[1].\n \n <path>::\n \n-- \n1.5.0.rc1.g556b\n"}]}