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

Re: [PATCH] docs: .gitignore parsing is to the top of the repo

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 7, 2021, 00:18 UTC
Message-ID
<xmqqr1gbf02i.fsf@gitster.g>
In-Reply-To
<xmqqk0m3gl6a.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
Show 24 quoted lines
> Andrew Berry <andrew@furrypaws.ca> writes:
>
>>   * Patterns read from a `.gitignore` file in the same directory
>> -   as the path, or in any parent directory, with patterns in the
>> -   higher level files (up to the toplevel of the work tree) being overridden
>> -   by those in lower level files down to the directory containing the file.
>> -   These patterns match relative to the location of the
>> -   `.gitignore` file.  A project normally includes such
>> -   `.gitignore` files in its repository, containing patterns for
>> +   as the path, or in any parent directory (up to the top-level of the work
>> +   tree), with patterns in the higher level files being overridden by those in
>> +   lower level files down to the directory containing the file. These patterns
>> +   match relative to the location of the `.gitignore` file.  A project normally
>> +   includes such `.gitignore` files in its repository, containing patterns for
>>     files generated as part of the project build.
>
> Line rewrapping makes it hard to see what actually got changed, but
> does this only move "(up to the top-level of the work tree)" around
> without anything else, as discussed?
>
> If you do "toplevel" -> "top-level" while at it, perhaps we would
> want to correct "work tree" -> "working tree".
>
> Looking better.

Another tangent. The discovery process used for the .gitattributes files is identical to what is done to the .gitignore files; we may want to make sure that the explanation we give in our documentation won't cause the same confusion you are trying to avoid with this change. Such a fix does not have to be (and probably should not be) a part of this change, though.

Thanks.
Previous: Junio C HamanoNext: Andrew Berry
Message 11 of 16 in “docs: .gitignore in parents is current repo only”
  1. docs: .gitignore in parents is current repo onlyAndrew Berry, Jul 2, 2021
  2. Junio C HamanoJul 3, 2021
  3. Bagas SanjayaJul 3, 2021
  4. Andrew BerryJul 5, 2021
  5. Junio C HamanoJul 5, 2021
  6. Andrew BerryJul 5, 2021
  7. Junio C HamanoJul 6, 2021
  8. docs: .gitignore parsing is to the top of the repoAndrew Berry, Jul 6, 2021
  9. docs: .gitignore parsing is to the top of the repoAndrew Berry, Jul 6, 2021
  10. Junio C HamanoJul 6, 2021
  11. Junio C HamanoJul 7, 2021
  12. Andrew BerryJul 7, 2021
  13. Junio C HamanoJul 7, 2021
  14. Andrew BerryJul 18, 2021
  15. Junio C HamanoJul 19, 2021
  16. Junio C HamanoJul 6, 2021

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.