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

Re: .gitignore, .gitattributes, .gitmodules, .gitprecious?,.gitacls? etc.

From
JHJan Hudec <bulb@ucw.cz>
Date
Sep 4, 2007, 20:23 UTC
Message-ID
<20070904202326.GC3786@efreet.light.src>
In-Reply-To
<Pine.LNX.4.64.0708280945350.28586@racer.site>
On Tue, Aug 28, 2007 at 09:49:47 +0100, Johannes Schindelin wrote:
Show 19 quoted lines
> Hi,
> 
> On Mon, 27 Aug 2007, Dmitry Kakurin wrote:
> 
> > Here is the problem: we need to apply crlf attributes to a file. We
> > could have .gitattributes both in the index and in the worktree.
> > Which one do we use?
> > In general .gitattributes file could be (U)nchanged, (C)hanged, (NP)
> > NotPresent in each place.
> 
> I do not see these cases.  You can have these cases, basically:
> 
> - .gitattributes in worktree (then it does not matter what else we have),
> - .gitattributes not in the worktree, but in the index (then that is taken)
> 
> In the latter case, there could be conflicts _in_ .gitattributes, in which 
> case those .gitattributes are ignored.
> 
> I do not see any problem with that.
I do.
IMNSHO it should be the other way around:
 .gitattributes in index, than index version is used.
 .gitattributes not in index, but in worktree, than that tree version is used.

Why? Because when you check out another version, the .gitattributes commited in that version need to be applied, since it might be different from whatever is currently in the tree.

In the other direction, the tree version seems to make more sense, but in reality it does not. If you do a partial commit of a single file, than the index version gets into the commit, so that should better be the version used to store the file. On the other hand if you change .gitattributes, the normal commit rules are that you need to add it for commit, so needing to add it to make it effective goes well together with it. update-index would need to always handle .git* before other entries to make add . and commit -a work correctly.

The case for worktree only is for cases when you for some reason want to have local .gitattributes. Though I am not sure that should actually work, because you couldn't have local .gitattributes if there is versioned version. .git/info/attributes would be better for that. Which gets us back to "always use .gitattributes from *index*" (and read it from tree before other files when adding it).

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
Previous: Dmitry KakurinNext: Dmitry Kakurin
Message 23 of 28 in “.gitignore, .gitattributes, .gitmodules, .gitprecious?, .gitacls? etc.”
  1. Dmitry KakurinAug 26, 2007
  2. Junio C HamanoAug 26, 2007
  3. Dmitry KakurinAug 26, 2007
  4. Junio C HamanoAug 26, 2007
  5. Dmitry KakurinAug 26, 2007
  6. Junio C HamanoAug 26, 2007
  7. Dmitry KakurinAug 26, 2007
  8. Petr BaudisAug 26, 2007
  9. Sam VilainAug 27, 2007
  10. David KastrupAug 27, 2007
  11. Sam VilainAug 27, 2007
  12. David KastrupAug 27, 2007
  13. Johannes SchindelinAug 27, 2007
  14. Johannes SchindelinAug 26, 2007
  15. martin f krafftAug 27, 2007
  16. Sergio CallegariAug 27, 2007
  17. David KastrupAug 27, 2007
  18. Petr BaudisAug 27, 2007
  19. Sergio CallegariAug 27, 2007
  20. Sergio CallegariAug 27, 2007
  21. Jan HudecSep 4, 2007
  22. .gitignore, .gitattributes, .gitmodules, .gitprecious?,.gitacls? etc.Dmitry Kakurin, Aug 27, 2007
  23. Jan HudecSep 4, 2007
  24. Dmitry KakurinSep 5, 2007
  25. Junio C HamanoSep 5, 2007
  26. Dmitry KakurinSep 5, 2007
  27. Jan HudecSep 5, 2007
  28. Jan HudecSep 4, 2007

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.