{"thread":{"id":"632","subject":"Re: git repository for net drivers available","startedAt":"2005-05-15T20:05:14Z","lastAt":"2005-05-15T21:46:11Z","messageCount":3,"participants":["Petr Baudis","Jeff Garzik","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"3381","messageId":"20050515200514.GA31414@pasky.ji.cz","threadId":"632","inReplyTo":"4284C7DA.1020707@pobox.com","subject":"Re: git repository for net drivers available","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-05-15T20:05:14Z","receivedAt":"2005-05-15T20:05:14Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Fri, May 13, 2005 at 05:29:30PM CEST, I got a letter\nwhere Jeff Garzik <jgarzik@pobox.com> told me that...\n> Looks like cogito is using $repo/heads/$branch, whereas my git repo is \n> using $repo/branches/$branch.\n\nWould it be a big problem to use refs/heads/$branch? That's the\ncurrently commonly agreed convention about location for storing branch\nheads, not just some weird Cogito-specific invention. And it'd be very\nnice to have those locations consistent across git repositories.\n\nThanks,\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"3383","messageId":"4287AF22.8090300@pobox.com","threadId":"632","inReplyTo":"20050515200514.GA31414@pasky.ji.cz","subject":"Re: git repository for net drivers available","fromName":"Jeff Garzik","fromEmail":"jgarzik@pobox.com","sentAt":"2005-05-15T20:20:50Z","receivedAt":"2005-05-15T20:20:50Z","isPatch":false,"sender":{"key":"jgarzik@pobox.com","avatar":null},"body":"Petr Baudis wrote:\n> Dear diary, on Fri, May 13, 2005 at 05:29:30PM CEST, I got a letter\n> where Jeff Garzik <jgarzik@pobox.com> told me that...\n> \n>>Looks like cogito is using $repo/heads/$branch, whereas my git repo is \n>>using $repo/branches/$branch.\n> \n> \n> Would it be a big problem to use refs/heads/$branch? That's the\n> currently commonly agreed convention about location for storing branch\n> heads, not just some weird Cogito-specific invention. And it'd be very\n> nice to have those locations consistent across git repositories.\n\nSure, that's doable.\n\nI've pushed out this change to kernel.org.\n\n\tJeff\n\n\n\n"},{"id":"3399","messageId":"7vacmwqi1o.fsf@assigned-by-dhcp.cox.net","threadId":"632","inReplyTo":"20050515200514.GA31414@pasky.ji.cz","subject":"Re: git repository for net drivers available","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-05-15T21:46:11Z","receivedAt":"2005-05-15T21:46:11Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":">>>>> \"PB\" == Petr Baudis <pasky@ucw.cz> writes:\n\nPB> Dear diary, on Fri, May 13, 2005 at 05:29:30PM CEST, I got a letter\nPB> where Jeff Garzik <jgarzik@pobox.com> told me that...\n>> Looks like cogito is using $repo/heads/$branch, whereas my git repo is \n>> using $repo/branches/$branch.\n\nPB> Would it be a big problem to use refs/heads/$branch? That's the\nPB> currently commonly agreed convention about location for storing branch\nPB> heads, not just some weird Cogito-specific invention. And it'd be very\nPB> nice to have those locations consistent across git repositories.\n\nSince Jeff brought up $repo/branches/$branch, you may also want\nto add that $repo/branches/$branch is used to record the URL of\nthe remote $branch (the information used to be in a flat file\n$repo/remotes, branch name and URL separated by shell $IFS, one\nrecord on each line), and is quite different from those 40-byte\nSHA1 plus LF files you see in $repo/refs/*/ directory.\n\nI think it is a reasonable one, I also follow the\n$repo/branches/$branch convention Cogito uses, and I would\nencorage other Porcelain implementations to follow suit.\n\n"}]}