{"thread":{"id":"43484","subject":"Re: [ANNOUNCE] gitfs pre-release 0.04","startedAt":"2006-12-04T19:40:11Z","lastAt":"2006-12-04T20:03:49Z","messageCount":4,"participants":["Mitchell Blank Jr","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"296242","messageId":"20061204194011.GW47959@gaz.sfgoth.com","threadId":"43484","inReplyTo":null,"subject":"[ANNOUNCE] gitfs pre-release 0.04","fromName":"Mitchell Blank Jr","fromEmail":"mitch@sfgoth.com","sentAt":"2006-12-04T19:40:11Z","receivedAt":"2006-12-04T19:40:11Z","isPatch":false,"sender":{"key":"mitch@sfgoth.com","avatar":null},"body":"I've uploaded another pre-release of my gitfs tool.  I haven't had much time\nto work on it lately, so not much has changed since the last release a\nyear ago:\n\thttp://www.gelato.unsw.edu.au/archives/git/0511/12617.html\n\nHowever that version no longer works (or even compiles against :-) the\nFUSE API in recent linux kernels so I figured a fresh tarball would\nbe nice.\n\nChanges:\n  * Added a configuration subsystem.  Isn't used for much yet\n\n  * At the top of each tree there's now a synthetic \".git\" directory\n    which includes some symlinks and a \"HEAD\" file that points to\n    the currently viewed root.  The idea is to allow some simple git\n    commands to work inside of a gitfs directory.  Unfortunately this doesn't\n    work yet since git no longer recognizes a non-symbolic ref in \"HEAD\".\n    I'll try to work around this soon.\n\n  * Various bug-fixes, etc\n\nAs usual tarballs are available at:\n\thttp://www.sfgoth.com/~mitch/linux/gitfs/\nSorry, I still haven't set up a git repository for it yet.\n\n"},{"id":"296046","messageId":"el1tg0$n07$1@sea.gmane.org","threadId":"43484","inReplyTo":"20061204194011.GW47959@gaz.sfgoth.com","subject":"Re: [ANNOUNCE] gitfs pre-release 0.04","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-12-04T19:40:38Z","receivedAt":"2006-12-04T19:40:38Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Mitchell Blank Jr wrote:\n\n>   * At the top of each tree there's now a synthetic \".git\" directory\n>     which includes some symlinks and a \"HEAD\" file that points to\n>     the currently viewed root.  The idea is to allow some simple git\n>     commands to work inside of a gitfs directory.  Unfortunately this doesn't\n>     work yet since git no longer recognizes a non-symbolic ref in \"HEAD\".\n>     I'll try to work around this soon.\n\nNot true. Symlink HEAD still works, and we have even core.preferSymlinkRefs\nconfiguration variable.\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n\n"},{"id":"297467","messageId":"200612042054.34157.jnareb@gmail.com","threadId":"43484","inReplyTo":"20061204200349.GX47959@gaz.sfgoth.com","subject":"Re: [ANNOUNCE] gitfs pre-release 0.04","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-12-04T19:54:33Z","receivedAt":"2006-12-04T19:54:33Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Mitchell Blank Jr wrote:\n> Jakub Narebski wrote:\n>\n>> Not true. Symlink HEAD still works, and we have even core.preferSymlinkRefs\n>> configuration variable.\n> \n> Yes, but it has to be a symlink pointing into \"refs/\", not just a regular\n> file holding a hash value.  Which is fine for most purposes but sort of a\n> pain for me.\n> \n> I'll probably have it be a symlink to \"refs/gitfs-dynamic\" or something and\n> then have \"refs\" be populated with that synthetic file and symlinks to\n> any of the normal contents of the refs directory.  Not too bad, but will\n> take a little bit of code.\n\nYou would have to wait a bit. There was talk on git mailing list about\nallowing HEAD to point to non-head ref, or even bare sha1, only forbidding\ncommitting to such HEAD (but allowing checkout of arbitrary revision,\nnot only branch, but also remote branch, tag, or branch~n).\n-- \nJakub Narebski\n"},{"id":"295058","messageId":"20061204200349.GX47959@gaz.sfgoth.com","threadId":"43484","inReplyTo":"el1tg0$n07$1@sea.gmane.org","subject":"Re: [ANNOUNCE] gitfs pre-release 0.04","fromName":"Mitchell Blank Jr","fromEmail":"mitch@sfgoth.com","sentAt":"2006-12-04T20:03:49Z","receivedAt":"2006-12-04T20:03:49Z","isPatch":false,"sender":{"key":"mitch@sfgoth.com","avatar":null},"body":"Jakub Narebski wrote:\n> Not true. Symlink HEAD still works, and we have even core.preferSymlinkRefs\n> configuration variable.\n\nYes, but it has to be a symlink pointing into \"refs/\", not just a regular\nfile holding a hash value.  Which is fine for most purposes but sort of a\npain for me.\n\nI'll probably have it be a symlink to \"refs/gitfs-dynamic\" or something and\nthen have \"refs\" be populated with that synthetic file and symlinks to\nany of the normal contents of the refs directory.  Not too bad, but will\ntake a little bit of code.\n\n"}]}