{"thread":{"id":"13810","subject":"[PATCH] git-for-each-ref.txt: fix description of <pattern>","startedAt":"2008-06-05T11:19:12Z","lastAt":"2008-06-05T21:01:38Z","messageCount":6,"participants":["Lea Wiemann","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"78745","messageId":"1212664752-12160-1-git-send-email-LeWiemann@gmail.com","threadId":"13810","inReplyTo":null,"subject":"[PATCH] git-for-each-ref.txt: fix description of <pattern>","fromName":"Lea Wiemann","fromEmail":"lewiemann@gmail.com","sentAt":"2008-06-05T11:19:12Z","receivedAt":"2008-06-05T11:19:12Z","isPatch":true,"sender":{"key":"lewiemann@gmail.com","avatar":null},"body":"git-for-each-ref supports not only glob patterns but also prefixes\nlike \"refs/heads\" as patterns.  This documents it.\n\nSigned-off-by: Lea Wiemann <LeWiemann@gmail.com>\n---\n Documentation/git-for-each-ref.txt |    6 +++---\n 1 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex f1f90cc..a9633c6 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -48,9 +48,9 @@ OPTIONS\n \t`%09` to `\\t` (TAB) and `%0a` to `\\n` (LF).\n \n <pattern>::\n-\tIf given, the name of the ref is matched against this\n-\tusing fnmatch(3).  Refs that do not match the pattern\n-\tare not shown.\n+\tIf given, only refs are shown that match againt the pattern\n+\teither using fnmatch(3) or literally, in the latter case up to\n+\ta slash or entirely.\n \n --shell, --perl, --python, --tcl::\n \tIf given, strings that substitute `%(fieldname)`\n-- \n1.5.6.rc1.9.g69bbf.dirty\n"},{"id":"78772","messageId":"1212673114-15751-1-git-send-email-LeWiemann@gmail.com","threadId":"13810","inReplyTo":"1212664752-12160-1-git-send-email-LeWiemann@gmail.com","subject":"[PATCH v2] git-for-each-ref.txt: minor improvements","fromName":"Lea Wiemann","fromEmail":"lewiemann@gmail.com","sentAt":"2008-06-05T13:38:34Z","receivedAt":"2008-06-05T13:38:34Z","isPatch":true,"sender":{"key":"lewiemann@gmail.com","avatar":null},"body":"From: Lea Wiemann <lewiemann@gmail.com>\n\nRewrapped synopsis and removed wrong asterisk behind --count option;\nclarified --sort=<key> description for multiple keys; documented that\nfor-each-ref supports not only glob patterns but also prefixes like\n\"refs/heads\" as patterns.\n\nSigned-off-by: Lea Wiemann <LeWiemann@gmail.com>\n---\nAdded more fixes/improvements since v1.\n\n Documentation/git-for-each-ref.txt |   14 +++++++-------\n 1 files changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex f1f90cc..4ffc65f 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -8,8 +8,7 @@ git-for-each-ref - Output information on each ref\n SYNOPSIS\n --------\n [verse]\n-'git-for-each-ref' [--count=<count>]\\*\n-                   [--shell|--perl|--python|--tcl]\n+'git-for-each-ref' [--count=<count>] [--shell|--perl|--python|--tcl]\n                    [--sort=<key>]\\* [--format=<format>] [<pattern>]\n \n DESCRIPTION\n@@ -32,8 +31,9 @@ OPTIONS\n <key>::\n \tA field name to sort on.  Prefix `-` to sort in\n \tdescending order of the value.  When unspecified,\n-\t`refname` is used.  More than one sort keys can be\n-\tgiven.\n+\t`refname` is used.  You may use the --sort=<key> option\n+\tmultiple times, in which case the last key becomes the primary\n+\tkey.\n \n <format>::\n \tA string that interpolates `%(fieldname)` from the\n@@ -48,9 +48,9 @@ OPTIONS\n \t`%09` to `\\t` (TAB) and `%0a` to `\\n` (LF).\n \n <pattern>::\n-\tIf given, the name of the ref is matched against this\n-\tusing fnmatch(3).  Refs that do not match the pattern\n-\tare not shown.\n+\tIf given, only refs are shown that match againt the pattern\n+\teither using fnmatch(3) or literally, in the latter case up to\n+\ta slash or entirely.\n \n --shell, --perl, --python, --tcl::\n \tIf given, strings that substitute `%(fieldname)`\n-- \n1.5.6.rc1.9.g69bbf.dirty\n"},{"id":"78795","messageId":"1212691205-24399-1-git-send-email-LeWiemann@gmail.com","threadId":"13810","inReplyTo":"1212673114-15751-1-git-send-email-LeWiemann@gmail.com","subject":"[PATCH v3] git-for-each-ref.txt: minor improvements","fromName":"Lea Wiemann","fromEmail":"lewiemann@gmail.com","sentAt":"2008-06-05T18:40:05Z","receivedAt":"2008-06-05T18:40:05Z","isPatch":true,"sender":{"key":"lewiemann@gmail.com","avatar":null},"body":"From: Lea Wiemann <lewiemann@gmail.com>\n\nRewrapped synopsis and removed wrong asterisk behind --count option;\nclarified --sort=<key> description for multiple keys; documented that\nfor-each-ref supports not only glob patterns but also prefixes like\n\"refs/heads\" as patterns, and that multiple patterns can be given.\n\nSigned-off-by: Lea Wiemann <LeWiemann@gmail.com>\n---\nChanged since v2: Also document that multiple patterns can be given.\n\n Documentation/git-for-each-ref.txt |   16 ++++++++--------\n 1 files changed, 8 insertions(+), 8 deletions(-)\n\ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex f1f90cc..2ff4c2d 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -8,9 +8,8 @@ git-for-each-ref - Output information on each ref\n SYNOPSIS\n --------\n [verse]\n-'git-for-each-ref' [--count=<count>]\\*\n-                   [--shell|--perl|--python|--tcl]\n-                   [--sort=<key>]\\* [--format=<format>] [<pattern>]\n+'git-for-each-ref' [--count=<count>] [--shell|--perl|--python|--tcl]\n+                   [--sort=<key>]\\* [--format=<format>] [<pattern>...]\n \n DESCRIPTION\n -----------\n@@ -32,8 +31,9 @@ OPTIONS\n <key>::\n \tA field name to sort on.  Prefix `-` to sort in\n \tdescending order of the value.  When unspecified,\n-\t`refname` is used.  More than one sort keys can be\n-\tgiven.\n+\t`refname` is used.  You may use the --sort=<key> option\n+\tmultiple times, in which case the last key becomes the primary\n+\tkey.\n \n <format>::\n \tA string that interpolates `%(fieldname)` from the\n@@ -48,9 +48,9 @@ OPTIONS\n \t`%09` to `\\t` (TAB) and `%0a` to `\\n` (LF).\n \n <pattern>::\n-\tIf given, the name of the ref is matched against this\n-\tusing fnmatch(3).  Refs that do not match the pattern\n-\tare not shown.\n+\tIf one or more patterns are given, only refs are shown that\n+\tmatch againt at least one pattern, either using fnmatch(3) or\n+\tliterally, in the latter case up to a slash or entirely.\n \n --shell, --perl, --python, --tcl::\n \tIf given, strings that substitute `%(fieldname)`\n-- \n1.5.6.rc1.9.g69bbf.dirty\n"},{"id":"78799","messageId":"7vwsl31zfq.fsf@gitster.siamese.dyndns.org","threadId":"13810","inReplyTo":"1212691205-24399-1-git-send-email-LeWiemann@gmail.com","subject":"Re: [PATCH v3] git-for-each-ref.txt: minor improvements","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-06-05T18:58:33Z","receivedAt":"2008-06-05T18:58:33Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Lea Wiemann <lewiemann@gmail.com> writes:\n\n>  <pattern>::\n> -\tIf given, the name of the ref is matched against this\n> -\tusing fnmatch(3).  Refs that do not match the pattern\n> -\tare not shown.\n> +\tIf one or more patterns are given, only refs are shown that\n> +\tmatch againt at least one pattern, either using fnmatch(3) or\n> +\tliterally, in the latter case up to a slash or entirely.\n\nThanks.  I suspect we might want to make it even more explicit that this\nis \"match from the beginning\" unlike what git-show-ref does, but your\npatch is an improvement even as-is.\n"},{"id":"78821","messageId":"1212699255-26640-1-git-send-email-LeWiemann@gmail.com","threadId":"13810","inReplyTo":"7vwsl31zfq.fsf@gitster.siamese.dyndns.org","subject":"[PATCH] git-for-each-ref.txt: minor fixes","fromName":"Lea Wiemann","fromEmail":"lewiemann@gmail.com","sentAt":"2008-06-05T20:54:15Z","receivedAt":"2008-06-05T20:54:15Z","isPatch":true,"sender":{"key":"lewiemann@gmail.com","avatar":null},"body":"From: Lea Wiemann <lewiemann@gmail.com>\n\nRewrapped synopsis and removed wrong asterisk behind --count option;\nclarified --sort=<key> description for multiple keys; documented that\nfor-each-ref supports not only glob patterns but also prefixes like\n\"refs/heads\" as patterns, and that multiple patterns can be given.\n\nSigned-off-by: Lea Wiemann <LeWiemann@gmail.com>\n---\nJunio C Hamano wrote:\n> I suspect we might want to make it even more explicit that this\n> is \"match from the beginning\"\n\nSure; see if you like this one (the only change since v3 is under\n<pattern>) or v3 better.\n\n Documentation/git-for-each-ref.txt |   17 +++++++++--------\n 1 files changed, 9 insertions(+), 8 deletions(-)\n\ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex f1f90cc..87c8389 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -8,9 +8,8 @@ git-for-each-ref - Output information on each ref\n SYNOPSIS\n --------\n [verse]\n-'git-for-each-ref' [--count=<count>]\\*\n-                   [--shell|--perl|--python|--tcl]\n-                   [--sort=<key>]\\* [--format=<format>] [<pattern>]\n+'git-for-each-ref' [--count=<count>] [--shell|--perl|--python|--tcl]\n+                   [--sort=<key>]\\* [--format=<format>] [<pattern>...]\n \n DESCRIPTION\n -----------\n@@ -32,8 +31,9 @@ OPTIONS\n <key>::\n \tA field name to sort on.  Prefix `-` to sort in\n \tdescending order of the value.  When unspecified,\n-\t`refname` is used.  More than one sort keys can be\n-\tgiven.\n+\t`refname` is used.  You may use the --sort=<key> option\n+\tmultiple times, in which case the last key becomes the primary\n+\tkey.\n \n <format>::\n \tA string that interpolates `%(fieldname)` from the\n@@ -48,9 +48,10 @@ OPTIONS\n \t`%09` to `\\t` (TAB) and `%0a` to `\\n` (LF).\n \n <pattern>::\n-\tIf given, the name of the ref is matched against this\n-\tusing fnmatch(3).  Refs that do not match the pattern\n-\tare not shown.\n+\tIf one or more patterns are given, only refs are shown that\n+\tmatch againt at least one pattern, either using fnmatch(3) or\n+\tliterally, in the latter case matching completely or from the\n+\tbeginning up to a slash.\n \n --shell, --perl, --python, --tcl::\n \tIf given, strings that substitute `%(fieldname)`\n-- \n1.5.6.rc1.9.g69bbf.dirty\n"},{"id":"78823","messageId":"1212699698-26935-1-git-send-email-LeWiemann@gmail.com","threadId":"13810","inReplyTo":"1212699255-26640-1-git-send-email-LeWiemann@gmail.com","subject":"[PATCH v5] git-for-each-ref.txt: minor improvements","fromName":"Lea Wiemann","fromEmail":"lewiemann@gmail.com","sentAt":"2008-06-05T21:01:38Z","receivedAt":"2008-06-05T21:01:38Z","isPatch":true,"sender":{"key":"lewiemann@gmail.com","avatar":null},"body":"Rewrapped synopsis and removed wrong asterisk behind --count option;\nclarified --sort=<key> description for multiple keys; documented that\nfor-each-ref supports not only glob patterns but also prefixes like\n\"refs/heads\" as patterns, and that multiple patterns can be given.\n\nSigned-off-by: Lea Wiemann <LeWiemann@gmail.com>\n---\n... and fixed the subject line.  Sorry for spamming the list!\n\n Documentation/git-for-each-ref.txt |   17 +++++++++--------\n 1 files changed, 9 insertions(+), 8 deletions(-)\n\ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex f1f90cc..87c8389 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -8,9 +8,8 @@ git-for-each-ref - Output information on each ref\n SYNOPSIS\n --------\n [verse]\n-'git-for-each-ref' [--count=<count>]\\*\n-                   [--shell|--perl|--python|--tcl]\n-                   [--sort=<key>]\\* [--format=<format>] [<pattern>]\n+'git-for-each-ref' [--count=<count>] [--shell|--perl|--python|--tcl]\n+                   [--sort=<key>]\\* [--format=<format>] [<pattern>...]\n \n DESCRIPTION\n -----------\n@@ -32,8 +31,9 @@ OPTIONS\n <key>::\n \tA field name to sort on.  Prefix `-` to sort in\n \tdescending order of the value.  When unspecified,\n-\t`refname` is used.  More than one sort keys can be\n-\tgiven.\n+\t`refname` is used.  You may use the --sort=<key> option\n+\tmultiple times, in which case the last key becomes the primary\n+\tkey.\n \n <format>::\n \tA string that interpolates `%(fieldname)` from the\n@@ -48,9 +48,10 @@ OPTIONS\n \t`%09` to `\\t` (TAB) and `%0a` to `\\n` (LF).\n \n <pattern>::\n-\tIf given, the name of the ref is matched against this\n-\tusing fnmatch(3).  Refs that do not match the pattern\n-\tare not shown.\n+\tIf one or more patterns are given, only refs are shown that\n+\tmatch againt at least one pattern, either using fnmatch(3) or\n+\tliterally, in the latter case matching completely or from the\n+\tbeginning up to a slash.\n \n --shell, --perl, --python, --tcl::\n \tIf given, strings that substitute `%(fieldname)`\n-- \n1.5.6.rc1.9.g69bbf.dirty\n"}]}