git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-gui: Fix file name pattern in .gitattributes.

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 24, 2009, 17:33 UTC
Message-ID
<7vskm3hh8n.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<49A3BD25.3000706@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
Show 30 quoted lines
> Junio C Hamano schrieb:
>> Johannes Sixt <j6t@kdbg.org> writes:
>> 
>>> The pattern for the *.po files was anchored at the repository's root, but
>>> this would match the files only in the git-gui repository itself, but
>>> not in the version that is subtree-merged into git.git.
>>>
>>> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
>>> ---
>>>  .gitattributes |    2 +-
>>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/.gitattributes b/.gitattributes
>>> index f96112d..c69f4a0 100644
>>> --- a/.gitattributes
>>> +++ b/.gitattributes
>>> @@ -1,3 +1,3 @@
>>>  *           encoding=US-ASCII
>>>  git-gui.sh  encoding=UTF-8
>>> -/po/*.po    encoding=UTF-8
>>> +po/*.po     encoding=UTF-8
>> 
>> Hmm, really?
>
> No, not really. =:{
>
> I observed some strangeness with gitk. But it turned out that this was an
> old development version that got accidentally installed somewhere in $PATH.
>
> Sorry for the noise.

Actually, while I was responding to your message, I looked at gitattributes documentation and noticed that it does not say anything about how the "glob" is used to match paths. The rules applied should be the same as those from gitignore (except obviously we do not have negated pattern that gitignore has, because it does not mean "path not matching this pattern" over there), and it should be documented.

Previous: Johannes SixtNext: Johannes Sixt
Message 4 of 6 in “git-gui: Fix file name pattern in .gitattributes.”
  1. git-gui: Fix file name pattern in .gitattributes.Johannes Sixt, Feb 24, 2009
  2. Junio C HamanoFeb 24, 2009
  3. Johannes SixtFeb 24, 2009
  4. Junio C HamanoFeb 24, 2009
  5. 1/2 gitattributes.txt: Path matching rules are explained in gitignore.txtJohannes Sixt, Feb 25, 2009
  6. Johannes SixtFeb 25, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.