{"thread":{"id":"5953","subject":"[PATCH] Add revspec documentation for ':path', ':[0-3]:path' and git-describe","startedAt":"2006-10-19T03:04:55Z","lastAt":"2006-10-19T04:57:02Z","messageCount":3,"participants":["pclouds@gmail.com","Junio C Hamano","Nguyen Thai Ngoc Duy"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"29198","messageId":"20061019030455.GA10554@localhost","threadId":"5953","inReplyTo":null,"subject":"[PATCH] Add revspec documentation for ':path', ':[0-3]:path' and git-describe","fromName":"","fromEmail":"pclouds@gmail.com","sentAt":"2006-10-19T03:04:55Z","receivedAt":"2006-10-19T03:04:55Z","isPatch":true,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"\nSigned-off-by: Nguyễn Thái Ngọc Duy \n---\n Documentation/git-rev-parse.txt | 9 +++++++++\n 1 files changed, 9 insertions(+), 0 deletions(-)\n\nAs I'm not very good at English, please correct any mistake I made\n\ndiff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt\nindex 2f1306c..f8f4920 100644\n--- a/Documentation/git-rev-parse.txt\n+++ b/Documentation/git-rev-parse.txt\n@@ -119,11 +119,17 @@ syntax.\n name the same commit object if there are no other object in\n your repository whose object name starts with dae86e.\n \n+* The result of `git-describe`\n+\n * A symbolic ref name. E.g. 'master' typically means the commit\n object referenced by $GIT_DIR/refs/heads/master. If you\n happen to have both heads/master and tags/master, you can\n explicitly say 'heads/master' to tell git which one you mean.\n \n+* A colon at the beginning, followed by path name to specify\n+ a file in index. If you want to specify a file in a stage,\n+ use expression ':[0-3]:' instead.\n+\n * A suffix '@' followed by a date specification enclosed in a brace\n pair (e.g. '\\{yesterday\\}', '\\{1 month 2 weeks 3 days 1 hour 1\n second ago\\}' or '\\{1979-02-26 18:30:00\\}') to specify the value\n@@ -156,6 +162,9 @@ syntax.\n and dereference the tag recursively until a non-tag object is\n found.\n \n+* A suffix ':' followed by path name to specify a specific file\n+ in that commit/tag/tree.\n+\n Here is an illustration, by Jon Loeliger. Both node B and C are\n a commit parents of commit node A. Parent commits are ordered\n left-to-right.\n-- \n1.4.3.rc2.g0503-dirty\n"},{"id":"29202","messageId":"7vlkncx6d2.fsf@assigned-by-dhcp.cox.net","threadId":"5953","inReplyTo":"20061019030455.GA10554@localhost","subject":"Re: [PATCH] Add revspec documentation for ':path', ':[0-3]:path' and git-describe","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-10-19T04:43:53Z","receivedAt":"2006-10-19T04:43:53Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"> As I'm not very good at English, please correct any mistake I made\n\nThanks. I do not know about English, but I'd move things around\nto group them better. Most talk about committish but the\ncolon-path are about trees and blobs.\n\ndiff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt\nindex 2f1306c..412bafb 100644\n--- a/Documentation/git-rev-parse.txt\n+++ b/Documentation/git-rev-parse.txt\n@@ -111,7 +111,9 @@ SPECIFYING REVISIONS\n \n A revision parameter typically, but not necessarily, names a\n commit object. They use what is called an 'extended SHA1'\n-syntax.\n+syntax. Here are various ways to spell object names. The\n+ones listed near the end of this list are to name trees and\n+blobs contained in a commit.\n \n * The full SHA1 object name (40-byte hexadecimal string), or\n a substring of such that is unique within the repository.\n@@ -119,6 +121,9 @@ syntax.\n name the same commit object if there are no other object in\n your repository whose object name starts with dae86e.\n \n+* An output from `git-describe`; i.e. a closest tag, followed by a\n+ dash, a 'g', and an abbreviated object name.\n+\n * A symbolic ref name. E.g. 'master' typically means the commit\n object referenced by $GIT_DIR/refs/heads/master. If you\n happen to have both heads/master and tags/master, you can\n@@ -156,6 +161,15 @@ syntax.\n and dereference the tag recursively until a non-tag object is\n found.\n \n+* A suffix ':' followed by a path; this names the blob or tree\n+ at the given path in the tree-ish object named by the part\n+ before the colon.\n+\n+* A colon, optionally followed by a stage number (0 to 3) and a\n+ colon, followed by a path; this names a blob object in the\n+ index at the given path. Missing stage number (and the colon\n+ that follows it) names an stage 0 entry.\n+\n Here is an illustration, by Jon Loeliger. Both node B and C are\n a commit parents of commit node A. Parent commits are ordered\n left-to-right.\n"},{"id":"29204","messageId":"fcaeb9bf0610182157i7cce5007r9552b2bf06988326@mail.gmail.com","threadId":"5953","inReplyTo":"7vlkncx6d2.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH] Add revspec documentation for ':path', ':[0-3]:path' and git-describe","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2006-10-19T04:57:02Z","receivedAt":"2006-10-19T04:57:02Z","isPatch":true,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On 10/19/06, Junio C Hamano wrote:\n> > As I'm not very good at English, please correct any mistake I made\n>\n> Thanks. I do not know about English, but I'd move things around\n> to group them better. Most talk about committish but the\n> colon-path are about trees and blobs.\n\nIt's ok to me.\n-- \nDuy\n"}]}