{"thread":{"id":"46024","subject":"Another git repo at kernel.org?","startedAt":"2017-05-22T18:34:08Z","lastAt":"2017-05-24T00:15:54Z","messageCount":5,"participants":["Stefan Beller","Ævar Arnfjörð Bjarmason","Theodore Ts'o","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"320458","messageId":"CAGZ79kYirjV0eQgB_ng-64HSPN_7njUMjnoNBkmWnx-rinsemQ@mail.gmail.com","threadId":"46024","inReplyTo":null,"subject":"Another git repo at kernel.org?","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2017-05-22T18:34:02Z","receivedAt":"2017-05-22T18:34:08Z","isPatch":false,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"Hi,\n\nThe Git community considers using submodules for some parts of the\ncode (a third party lib, SHA1DC, computing SHA1s that warn about\npotential attachs, see shattered.io) [1].\n\nWe are also concerned about single point of failure there, so a repo\nat kernel.org\nmirroring the potential submodule[2] would be great.\n\nI cc'd the git mailing list as we may want to have further discussion who\nshall have access to the new repo.\n\nThanks,\nStefan\n\n[1] https://public-inbox.org/git/20170520115429.12289-1-avarab@gmail.com/\n[2] https://github.com/cr-marcstevens/sha1collisiondetection\n"},{"id":"320464","messageId":"CACBZZX7HYU1USdcX_=CDFiMDtdaySSjd0zv-Bb1Z9-nHxk8UvQ@mail.gmail.com","threadId":"46024","inReplyTo":"CAGZ79kYirjV0eQgB_ng-64HSPN_7njUMjnoNBkmWnx-rinsemQ@mail.gmail.com","subject":"Re: Another git repo at kernel.org?","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2017-05-22T19:43:26Z","receivedAt":"2017-05-22T19:43:58Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"On Mon, May 22, 2017 at 8:34 PM, Stefan Beller wrote:\n> The Git community considers using submodules for some parts of the\n> code (a third party lib, SHA1DC, computing SHA1s that warn about\n> potential attachs, see shattered.io) [1].\n>\n> We are also concerned about single point of failure there, so a repo\n> at kernel.org\n> mirroring the potential submodule[2] would be great.\n>\n> I cc'd the git mailing list as we may want to have further discussion who\n> shall have access to the new repo.\n>\n> [1] https://public-inbox.org/git/20170520115429.12289-1-avarab@gmail.com/\n> [2] https://github.com/cr-marcstevens/sha1collisiondetection\n\nThe access problem could be solved by none of us having access to the\nrepo, if the git.kernel.org admins are willing to set up a mirror of\nthe github repo, a cronjob running git-fetch with the appropriate\nparameters to just fetch the master (or everything, but only master is\nneeded). Updating such a mirror with a daily cronjob would be more\nthan enough.\n\nLess seriously but worth pointing out: It could also be solved by just\nsetting the user:password to foo:bar and publishing that in the\ndescription & setting the repo to non-fast-forward only. This will\nonly be used by the git.git repo, which'll point at a specific sha1 in\nits history, wouldn't that be a nice demo of the whole \"give the repo\nto your worst enemy but as long as you have the sha ... \" parable\nLinus posted on-list back in the day... :)\n"},{"id":"320560","messageId":"20170523151310.mhdhck5djmdlxrt4@thunk.org","threadId":"46024","inReplyTo":"CACBZZX7HYU1USdcX_=CDFiMDtdaySSjd0zv-Bb1Z9-nHxk8UvQ@mail.gmail.com","subject":"Re: Another git repo at kernel.org?","fromName":"Theodore Ts'o","fromEmail":"tytso@mit.edu","sentAt":"2017-05-23T15:13:10Z","receivedAt":"2017-05-23T15:13:23Z","isPatch":false,"sender":{"key":"tytso@mit.edu","avatar":"https://avatars.githubusercontent.com/u/51416?v=4"},"body":"So Junio owns the pub/scm/git/git.git tree on kernel.org, and he may\nalready have access to create new repo's under the pub/scm/git\nhierarchy. In which case we might not need to bug the kernel.org\nadministrators at all.\n\nAlso, I'll note that it is possible to set up some repo's such that a\ngroup of people have access to push to them. You'll see for example\non git.kernel.org that certain repositories have as their owner \"XFS\nFS Group\", or \"ARM64 Group\" or \"Intel Wireless Group\".\n\nCheers,\n\n\t\t\t\t\t- Ted\n\n"},{"id":"320604","messageId":"xmqq60grjgje.fsf@gitster.mtv.corp.google.com","threadId":"46024","inReplyTo":"20170523151310.mhdhck5djmdlxrt4@thunk.org","subject":"Re: Another git repo at kernel.org?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-05-23T23:32:21Z","receivedAt":"2017-05-23T23:32:28Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Theodore Ts'o writes:\n\n> So Junio owns the pub/scm/git/git.git tree on kernel.org, and he may\n> already have access to create new repo's under the pub/scm/git\n> hierarchy. In which case we might not need to bug the kernel.org\n> administrators at all.\n\nYes, sorry for a premature inquiry.\n"},{"id":"320606","messageId":"CAGZ79kZufFQ9wUa8u1usPuWt-KLgfSxdGiXipYXiQW+k_JvQpQ@mail.gmail.com","threadId":"46024","inReplyTo":"xmqq60grjgje.fsf@gitster.mtv.corp.google.com","subject":"Re: Another git repo at kernel.org?","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2017-05-24T00:15:47Z","receivedAt":"2017-05-24T00:15:54Z","isPatch":false,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Tue, May 23, 2017 at 4:32 PM, Junio C Hamano wrote:\n> Theodore Ts'o writes:\n>\n>> So Junio owns the pub/scm/git/git.git tree on kernel.org, and he may\n>> already have access to create new repo's under the pub/scm/git\n>> hierarchy. In which case we might not need to bug the kernel.org\n>> administrators at all.\n>\n> Yes, sorry for a premature inquiry.\n\nThanks for bearing with my premature questions.\nI just went off from https://www.kernel.org/category/contact-us.html\nto see what the workflow would look like. Knowing that Junio\nowns the complete pub/scm/git namespace is a good data point for\nour discussion.\n\nSorry,\nStefan\n"}]}