{"thread":{"id":"63756","subject":"[PATCH 0/1] doc: correct doc for glob pathspec","startedAt":"2025-07-08T02:46:10Z","lastAt":"2025-07-21T13:09:11Z","messageCount":5,"participants":["Russell Hanneken","Junio C Hamano","Kristoffer Haugsbakk"],"isPatch":true,"patchVersion":1,"patchTotal":1},"messages":[{"id":"521494","messageId":"20250708024507.62386-1-rhanneken@pobox.com","threadId":"63756","inReplyTo":null,"subject":"[PATCH 0/1] doc: correct doc for glob pathspec","fromName":"Russell Hanneken","fromEmail":"rhanneken@pobox.com","sentAt":"2025-07-08T02:45:06Z","receivedAt":"2025-07-08T02:46:10Z","isPatch":true,"sender":{"key":"rhanneken@pobox.com","avatar":"https://avatars.githubusercontent.com/u/12398928?v=4"},"body":"gitglossary(7) documents Git pathspecs, including \"glob\" pathspecs,\nprefixed by the magic word \"glob\". It states, incorrectly, that the glob\npattern \"**/foo\" is equivalent to \"foo\".\n\nI suspect this incorrect statement is the result of copying and pasting\nfrom gitignore(5).\n\nThis patch removes the incorrect statement.\n\nRussell Hanneken (1):\n  doc: correct doc for glob pathspec\n\n Documentation/glossary-content.adoc | 5 ++---\n 1 file changed, 2 insertions(+), 3 deletions(-)\n\n\nbase-commit: 16bd9f20a403117f2e0d9bcda6c6e621d3763e77\n-- \n2.34.1\n\n"},{"id":"521495","messageId":"20250708024507.62386-2-rhanneken@pobox.com","threadId":"63756","inReplyTo":"20250708024507.62386-1-rhanneken@pobox.com","subject":"[PATCH 1/1] doc: correct doc for glob pathspec","fromName":"Russell Hanneken","fromEmail":"rhanneken@pobox.com","sentAt":"2025-07-08T02:45:07Z","receivedAt":"2025-07-08T02:46:14Z","isPatch":true,"sender":{"key":"rhanneken@pobox.com","avatar":"https://avatars.githubusercontent.com/u/12398928?v=4"},"body":"gitglossary documents Git pathspecs. One type of pathspec is the \"glob\"\npathspec, prefixed with the magic word \"glob\".\n\nRegarding glob pathspecs, gitglossary says, '\"**/foo\" matches file or\ndirectory \"foo\" anywhere, the same as pattern \"foo\".' That last phrase\n('the same as pattern \"foo\") is incorrect. \"**/foo\" and \"foo\" are not\nequivalent. \"**/foo\" matches foo anywhere, but \"foo\" does not.\n\nThis change removes the incorrect phrase from the glob pathspec doc.\n\nSigned-off-by: Russell Hanneken <rhanneken@pobox.com>\n---\n Documentation/glossary-content.adoc | 5 ++---\n 1 file changed, 2 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/glossary-content.adoc b/Documentation/glossary-content.adoc\nindex 575c18f776..e423e4765b 100644\n--- a/Documentation/glossary-content.adoc\n+++ b/Documentation/glossary-content.adoc\n@@ -418,9 +418,8 @@ full pathname may have special meaning:\n \n  - A leading \"`**`\" followed by a slash means match in all\n    directories. For example, \"`**/foo`\" matches file or directory\n-   \"`foo`\" anywhere, the same as pattern \"`foo`\". \"`**/foo/bar`\"\n-   matches file or directory \"`bar`\" anywhere that is directly\n-   under directory \"`foo`\".\n+   \"`foo`\" anywhere. \"`**/foo/bar`\" matches file or directory \"`bar`\"\n+   anywhere that is directly under directory \"`foo`\".\n \n  - A trailing \"`/**`\" matches everything inside. For example,\n    \"`abc/**`\" matches all files inside directory \"abc\", relative\n-- \n2.34.1\n\n"},{"id":"521501","messageId":"xmqqikk3xog6.fsf@gitster.g","threadId":"63756","inReplyTo":"20250708024507.62386-2-rhanneken@pobox.com","subject":"Re: [PATCH 1/1] doc: correct doc for glob pathspec","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-08T05:04:57Z","receivedAt":"2025-07-08T05:04:59Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Russell Hanneken <rhanneken@pobox.com> writes:\n\n>   - A leading \"`**`\" followed by a slash means match in all\n>     directories. For example, \"`**/foo`\" matches file or directory\n> -   \"`foo`\" anywhere, the same as pattern \"`foo`\". \"`**/foo/bar`\"\n> -   matches file or directory \"`bar`\" anywhere that is directly\n> -   under directory \"`foo`\".\n> +   \"`foo`\" anywhere. \"`**/foo/bar`\" matches file or directory \"`bar`\"\n> +   anywhere that is directly under directory \"`foo`\".\n\nSo, the change is that the explanation that the pattern `foo` would\nmatch the same as what `**/foo` matches, i.e. a file or directory\nwhose name is `foo`, either at the top-level or in any subdirectory.\n\nSounds correct.\n\nWill queue.  Thanks.\n"},{"id":"521802","messageId":"DB8RSNI6D2D8.2OCZSLRSIFP55@pobox.com","threadId":"63756","inReplyTo":"xmqqikk3xog6.fsf@gitster.g","subject":"Re: [PATCH 1/1] doc: correct doc for glob pathspec","fromName":"Russell Hanneken","fromEmail":"rhanneken@pobox.com","sentAt":"2025-07-10T23:39:47Z","receivedAt":"2025-07-10T23:39:50Z","isPatch":true,"sender":{"key":"rhanneken@pobox.com","avatar":"https://avatars.githubusercontent.com/u/12398928?v=4"},"body":"On Tue Jul 8, 2025 at 1:05 AM EDT, Junio C Hamano wrote:\n>\n> Will queue.  Thanks.\n\nWas there something wrong with my patch? I haven't seen my change appear\nin the repository.\n\nRegards,\n\nRussell Hanneken\nrhanneken@pobox.com\n\n"},{"id":"522348","messageId":"2f8ed9f4-5aff-486a-90c2-dce7f7116ae9@app.fastmail.com","threadId":"63756","inReplyTo":"DB8RSNI6D2D8.2OCZSLRSIFP55@pobox.com","subject":"Re: [PATCH 1/1] doc: correct doc for glob pathspec","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-07-21T13:08:49Z","receivedAt":"2025-07-21T13:09:11Z","isPatch":true,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Fri, Jul 11, 2025, at 01:39, Russell Hanneken wrote:\n> On Tue Jul 8, 2025 at 1:05 AM EDT, Junio C Hamano wrote:\n>>\n>> Will queue.  Thanks.\n>\n> Was there something wrong with my patch? I haven't seen my change appear\n> in the repository.\n\nSee [here], `rh/doc-glob-pathspec-fix`.  It’s currently on the `next`\nbranch and will be merged to `master` next.\n\n[here]: https://lore.kernel.org/git/xmqqo6ti49fk.fsf@gitster.g/\n"}]}