{"thread":{"id":"15255","subject":"[PATCH/RFC] Clarified how pattern works in documentation to git-show-ref.","startedAt":"2008-08-28T20:37:16Z","lastAt":"2008-08-29T05:04:46Z","messageCount":2,"participants":["Garry Dolley","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"88968","messageId":"1219955836-10070-1-git-send-email-gdolley@arpnetworks.com","threadId":"15255","inReplyTo":null,"subject":"[PATCH/RFC] Clarified how pattern works in documentation to git-show-ref.","fromName":"Garry Dolley","fromEmail":"gdolley@arpnetworks.com","sentAt":"2008-08-28T20:37:16Z","receivedAt":"2008-08-28T20:37:16Z","isPatch":true,"sender":{"key":"gdolley@ucla.edu","avatar":"https://gravatar.com/avatar/b9ca98e2d5fd3a993ad695e8315f078b7ae364d2d1b637a6adecf8953a034dd2?d=mp&s=160"},"body":"Several people in #git, including myself, thought that the following would\nshow all refs:\n\n  git show-ref '*'\n\nSince that is not how the pattern patching works, clarification was needed\nin the documentation.\n\nSigned-off-by: Garry Dolley <gdolley@ucla.edu>\n---\n\nI think including a little more info in the docs regarding the pattern would\nbe helpful.  Comments?\n\nThis is my first patch, I tried to follow all the rules in the\nSubmittingPatches doc.  If I missed anything, I apologize.\n\n Documentation/git-show-ref.txt |    6 ++++--\n 1 files changed, 4 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt\nindex 2f173ff..5966450 100644\n--- a/Documentation/git-show-ref.txt\n+++ b/Documentation/git-show-ref.txt\n@@ -86,7 +86,8 @@ OPTIONS\n \n <pattern>...::\n \n-\tShow references matching one or more patterns.\n+\tShow references matching one or more patterns. The pattern is tail-matched,\n+\tachored on a '/' boundary; pattern does not accept globs.\n \n OUTPUT\n ------\n@@ -127,7 +128,8 @@ use:\n -----------------------------------------------------------------------------\n \n This will show \"refs/heads/master\" but also \"refs/remote/other-repo/master\",\n-if such references exists.\n+if such references exists. This will not match \"refs/heads/master2\", because\n+the pattern is tail-matched.\n \n When using the '--verify' flag, the command requires an exact path:\n \n-- \n1.6.0.1\n"},{"id":"89083","messageId":"7vtzd48l8x.fsf@gitster.siamese.dyndns.org","threadId":"15255","inReplyTo":"1219955836-10070-1-git-send-email-gdolley@arpnetworks.com","subject":"Re: [PATCH/RFC] Clarified how pattern works in documentation to git-show-ref.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-08-29T05:04:46Z","receivedAt":"2008-08-29T05:04:46Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Garry Dolley <gdolley@arpnetworks.com> writes:\n\n> Several people in #git, including myself, thought that the following would\n> show all refs:\n>\n>   git show-ref '*'\n>\n> Since that is not how the pattern patching works, clarification was needed\n> in the documentation.\n>\n> Signed-off-by: Garry Dolley <gdolley@ucla.edu>\n> ---\n>\n> I think including a little more info in the docs regarding the pattern would\n> be helpful.  Comments?\n\nWould be helpful.\n\nIt may be worthwhile to know that that \"pathspec\" limiting done by\nrevision traversal (\"git log\", \"git rev-list\") and diff is also without\nglobbing, but it is a head-match, and match is forced at '/' boundary.\n\nls-files and grep know how to glob, on the other hand.\n"}]}