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

Re: [1.8.0] Tracking empty directories

From
YDYann Dirson <dirson@bertin.fr>
Date
Feb 3, 2011, 11:07 UTC
Message-ID
<20110203120753.6636d0cd@chalon.bertin.fr>
Jonathan wrote:
Show 5 quoted lines
>What might make git nice as an interoperability tool is that it tracks
>the _relevant_ information for the history of a software project.
>Example of what is not relevant information and why that matters:
>
> http://thread.gmane.org/gmane.comp.version-control.git/53494

Hell, that message seems to even suggest a potential solution: use .gitattributes for tracking empty dirs. That way a post-change "git checkout-index" could find the info (from .gitattribute in the index) without confusing any pre-change tool.

For ease of use, some porcelain could possibly be taught to add empty directories into $GIT_DIR/.gitattribute (as well as checking whether an empty-dir entry has turned useless because it now has content, and any other administrative stuff we could want).

But that idea is linked to another issue, which could be the subject of a 1.8 proposal of its own: the handling of .gitattribute, for which only the checked-out version is taken into account:

http://marc.info/?l=git&m=126458888515166
-- 
Yann Dirson - Bertin Technologies
Message 1 of 1 in “Re: [1.8.0] Tracking empty directories”
  1. Yann DirsonFeb 3, 2011

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.