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

Re: Tracking empty directories

From
Jakub Narebski <jnareb@gmail.com>
Date
Feb 1, 2011, 18:31 UTC
Message-ID
<201102011931.40559.jnareb@gmail.com>
In-Reply-To
<20110201181509.GA2370@LK-Perkele-VI.localdomain>
Dnia wtorek 1. lutego 2011 19:15, Ilari Liusvaara napisał:
Show 15 quoted lines
> On Wed, Feb 02, 2011 at 12:54:35AM +0700, Nguyen Thai Ngoc Duy wrote:
> > On Wed, Feb 2, 2011 at 12:28 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> > 
> > Could it be done with an index extension? Interesting.
> > 
> > > Certainly one ought to register an extension name or bump the version
> > > number to avoid confusing gits that don't know about the feature.
> > 
> > Index extension with lowercase name are "necessary for correct
> > operation". Older git will abort on unknown required extensions. If
> > you add to the main part of the index, better bump version number.
> 
> Worse problem than the index: Tree entries. Those are actually transferable
> and IIRC older (current?) git versions don't handle empty subdirectories
> (pointing entry of type directory to empty tree hash) all too well...
What did you mean by "don't handle" here?  The following entry
  040000 tree 22d5826c087c4b9dcc72e2131c2cfb061403f7eb	empty

should be not a problem; empty tree is hardcoded and also shouldn't there be a problem with such object. Is the problem when checking out such tree (writing to index and/or working area)?

> Worse yet, there isn't easy way to break the tree parser to avoid current
> git versions from screwing things up (IIRC, when I tested, invalid octal
> numbers finally broke it, invalid file types didn't do the trick)...

Well, then 1.8.0 version could be good place to break backwards compatibility; we did similar thing when introducing submodule entries, isn't it?

-- 
Jakub Narebski
Poland
Previous: Ilari LiusvaaraNext: Ilari Liusvaara
Message 25 of 36 in “Features from GitSurvey 2010”
  1. Dmitry S. KravtsovJan 29, 2011
  2. Jonathan NiederJan 29, 2011
  3. Jakub NarebskiFeb 1, 2011
  4. Nguyen Thai Ngoc DuyFeb 1, 2011
  5. Shawn PearceFeb 1, 2011
  6. Shawn PearceFeb 1, 2011
  7. Nguyen Thai Ngoc DuyFeb 1, 2011
  8. Junio C HamanoFeb 1, 2011
  9. Nicolas PitreFeb 1, 2011
  10. Nguyen Thai Ngoc DuyFeb 1, 2011
  11. Shawn PearceFeb 1, 2011
  12. Nicolas PitreFeb 1, 2011
  13. Shawn PearceFeb 2, 2011
  14. Nicolas PitreFeb 2, 2011
  15. david@lang.hmFeb 2, 2011
  16. Geert BoschFeb 3, 2011
  17. Narrow clone (Re: features from GitSurvey 2010)Jonathan Nieder, Feb 3, 2011
  18. Geert BoschFeb 3, 2011
  19. Jonathan NiederFeb 3, 2011
  20. Jonathan NiederFeb 3, 2011
  21. Nicolas PitreFeb 3, 2011
  22. Tracking empty directoriesJonathan Nieder, Feb 1, 2011
  23. Nguyen Thai Ngoc DuyFeb 1, 2011
  24. Ilari LiusvaaraFeb 1, 2011
  25. Jakub NarebskiFeb 1, 2011
  26. Ilari LiusvaaraFeb 1, 2011
  27. Jonathan NiederFeb 1, 2011
  28. Jakub NarebskiFeb 1, 2011
  29. Nguyen Thai Ngoc DuyFeb 2, 2011
  30. Kevin P. FlemingFeb 2, 2011
  31. Nicolas PitreFeb 1, 2011
  32. big files in git was: Re: Features from GitSurvey 2010david@lang.hm, Feb 1, 2011
  33. Nicolas PitreFeb 3, 2011
  34. Matthieu MoyFeb 1, 2011
  35. Jonathan NiederFeb 1, 2011
  36. Matthieu MoyFeb 1, 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.