{"thread":{"id":"429","subject":"Just a note: .git/refs/snap/ is not standard","startedAt":"2005-05-02T01:54:51Z","lastAt":"2005-05-02T03:13:14Z","messageCount":2,"participants":["Junio C Hamano","Daniel Barkalow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"2351","messageId":"7vacneqtn8.fsf@assigned-by-dhcp.cox.net","threadId":"429","inReplyTo":null,"subject":"Just a note: .git/refs/snap/ is not standard","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-05-02T01:54:51Z","receivedAt":"2005-05-02T01:54:51Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Linus, \n\n    not that there is any \"de facto\" or any standard there, but\nthe name .git/refs/snap/ you lifted from the vicinity thing is\nnot something Cogito folks have.  My understanding is of their\nconcensus is that .git/refs have single level subdirectories\nlike 'heads' and 'tags', and there will be little 41-byte text\nfiles that look like .git/HEAD.  So you probably would want to\neither (1) readdir in .git/refs (to future proof) or (2) drop\nrefs/snap from the vicinity list for now (to not give special\ntreatment to JIT, which I myself do not mind ;-)).  Also if you\ngo route (2) drop \"refs\" itself as well.\n\n"},{"id":"2352","messageId":"Pine.LNX.4.21.0505012249460.30848-100000@iabervon.org","threadId":"429","inReplyTo":"7vacneqtn8.fsf@assigned-by-dhcp.cox.net","subject":"Re: Just a note: .git/refs/snap/ is not standard","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2005-05-02T03:13:14Z","receivedAt":"2005-05-02T03:13:14Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Sun, 1 May 2005, Junio C Hamano wrote:\n\n> Linus, \n> \n>     not that there is any \"de facto\" or any standard there, but\n> the name .git/refs/snap/ you lifted from the vicinity thing is\n> not something Cogito folks have.  My understanding is of their\n> concensus is that .git/refs have single level subdirectories\n> like 'heads' and 'tags', and there will be little 41-byte text\n> files that look like .git/HEAD.\n\nI was intending this to be a more general concensus (and you seem to have\nfollowed it with your \"snap\" subdirectory).\n\n> So you probably would want to either (1) readdir in .git/refs (to future\n> proof) or (2) drop refs/snap from the vicinity list for now (to not give\n> special treatment to JIT, which I myself do not mind ;-)).  Also if you\n> go route (2) drop \"refs\" itself as well.\n\nActually, my code was intended to take things like \"heads/master\" or\n\"tags/linux-2.6.13\", which are found under \"refs/\" (although I also check\nthat they don't start with \".\" and have exactly one \"/\", to enforce the\nnaming system). Making it \"heads/linus\" rather than \"linus\" is important\nfor writing the files, since you can't guess reliably what subdirectory\nthe user means; also, it is easier for dealing with HTTP servers, where\nyou don't know what to ask for.\n\n\t-Daniel\n*This .sig left intentionally blank*\n\n"}]}