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

Re: Restoring timestamps (Re: Branches & directories)

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 22, 2011, 23:21 UTC
Message-ID
<CAFzf2Xw6=BFsKauYTG-4cw0D_LzLSNb_wqz8dQJ83wJHNQXbdg@mail.gmail.com>
In-Reply-To
<CAE1pOi1+nnpnHAuhYsXcfFNUroW0JcDQKLu6D7YNrUwJg0tXPw@mail.gmail.com>
Hilco Wijbenga wrote:
> You mean an extra dotfile per file in the commit?
Let me step back a moment.

When you mentioned mtime, a switch went off and reminded me of the problem of metadata in general, especially owner and permissions. That problem is important for people keeping track of /etc or $HOME in version control (always a little dangerous because of the effect of a stray "git reset --hard", but never mind). And the last time it came up, I convinced myself that a hook script setting up entries in .gitattributes, .gitmetadata, or .etckeepr with information like "all files are owned by root:root unless otherwise specified" could be a good and not too invasive way to deal with that.

Now that you remind me that the mtime of every file is likely to differ from every other file, it is harder to imagine what situation would make this meaningful information that should be stored in the repository and shared with other people. It seems more like something associated to the worktree, which fits more closely with what you are trying to do, anyway.

Regarding the problem "eclipse metadata is not carried over from one worktree to another", isn't that going to be a problem regardless? In your proposed setup, each time you stash everything and start work on a different branch, the eclipse metadata before would be stashed along with everything else, which doesn't make anything any easier (unless disk space is very scarce or metadata stores the absolute path to the cwd).

Sorry for the lack of clarity. Jonathan

Previous: Hilco WijbengaNext: Hilco Wijbenga
Message 29 of 52 in “Branches & directories”
  1. Hilco WijbengaAug 17, 2011
  2. Evan ShelhamerAug 17, 2011
  3. Junio C HamanoAug 17, 2011
  4. Hilco WijbengaAug 17, 2011
  5. Jonathan NiederAug 18, 2011
  6. Hilco WijbengaAug 21, 2011
  7. Michael WittenAug 18, 2011
  8. Michael J GruberAug 18, 2011
  9. Michael WittenAug 18, 2011
  10. Jonathan NiederAug 19, 2011
  11. Hilco WijbengaAug 21, 2011
  12. Michael WittenAug 21, 2011
  13. Hilco WijbengaAug 21, 2011
  14. Michael WittenAug 21, 2011
  15. Hilco WijbengaAug 21, 2011
  16. Michael WittenAug 22, 2011
  17. Hilco WijbengaAug 22, 2011
  18. Hilco WijbengaAug 22, 2011
  19. Michael WittenAug 22, 2011
  20. Hilco WijbengaAug 22, 2011
  21. Kyle MoffettAug 22, 2011
  22. Hilco WijbengaAug 22, 2011
  23. Kyle MoffettAug 22, 2011
  24. Hilco WijbengaAug 22, 2011
  25. Kyle MoffettAug 22, 2011
  26. Hilco WijbengaAug 22, 2011
  27. Restoring timestamps (Re: Branches & directories)Jonathan Nieder, Aug 22, 2011
  28. Hilco WijbengaAug 22, 2011
  29. Jonathan NiederAug 22, 2011
  30. Hilco WijbengaAug 23, 2011
  31. Hilco WijbengaAug 23, 2011
  32. Enrico WeigeltOct 2, 2011
  33. Hilco WijbengaOct 2, 2011
  34. Michael WittenAug 23, 2011
  35. Robin RosenbergOct 2, 2011
  36. Ronan KeryellOct 2, 2011
  37. Matthieu MoyOct 2, 2011
  38. Hilco WijbengaOct 2, 2011
  39. Hilco WijbengaOct 2, 2011
  40. Jeff KingOct 3, 2011
  41. Hilco WijbengaOct 3, 2011
  42. Jeff KingOct 3, 2011
  43. Matthieu MoyOct 3, 2011
  44. Jeff KingOct 3, 2011
  45. Matthieu MoyOct 3, 2011
  46. Jeff KingOct 3, 2011
  47. Junio C HamanoOct 3, 2011
  48. Jeff KingOct 3, 2011
  49. Hilco WijbengaOct 3, 2011
  50. Robin RosenbergOct 3, 2011
  51. Hilco WijbengaOct 3, 2011
  52. Hilco WijbengaOct 2, 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.