{"thread":{"id":"28492","subject":"Symbolic refs and the git protocol?","startedAt":"2011-09-25T13:17:31Z","lastAt":"2011-09-26T14:49:09Z","messageCount":7,"participants":["Avi Kivity","Sitaram Chamarty","Ilari Liusvaara"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"176164","messageId":"4E7F29EB.8000800@redhat.com","threadId":"28492","inReplyTo":null,"subject":"Symbolic refs and the git protocol?","fromName":"Avi Kivity","fromEmail":"avi@redhat.com","sentAt":"2011-09-25T13:17:31Z","receivedAt":"2011-09-25T13:17:31Z","isPatch":false,"sender":{"key":"avi@redhat.com","avatar":null},"body":"With the old kernel.org setup, practically the only think I needed to do \non the server itself is the 'git symbolic-ref' command (used to point \nrefs/heads/linux-next at the correct stream).\n\nNow it looks like kernel.org will no longer offer shell access. Is it \npossible to support symbolic-ref via 'git push'?\n\n-- \nerror compiling committee.c: too many arguments to function\n"},{"id":"176169","messageId":"CAMK1S_joYUKPXDKyomFdbDP4H0UhcwtNQbC89gvNZOTHowYrLw@mail.gmail.com","threadId":"28492","inReplyTo":"4E7F29EB.8000800@redhat.com","subject":"Re: Symbolic refs and the git protocol?","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-09-25T13:42:24Z","receivedAt":"2011-09-25T13:42:24Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Sun, Sep 25, 2011 at 6:47 PM, Avi Kivity wrote:\n> With the old kernel.org setup, practically the only think I needed to do on\n> the server itself is the 'git symbolic-ref' command (used to point\n> refs/heads/linux-next at the correct stream).\n>\n> Now it looks like kernel.org will no longer offer shell access.  Is it\n> possible to support symbolic-ref via 'git push'?\n\nCan I assume you mean specifically for HEAD, as in 'git symbolic-ref\nHEAD refs/heads/some-branch'?\n\nAlthough gitolite disables shell access by design, it provides several\n(optionally installed) features to allow specific shell commands to be\nexecuted. One such command is \"set-head\", which does exactly what you\nask. You run it like 'ssh git@server set-head reponame.git\nrefs/heads/foo' and it ends up running 'git symbolic-ref HEAD\nrefs/heads/foo' in the repo.\n\nI realise that does not answer \"can it be done via git push\" but I\nthought it might help...\n"},{"id":"176170","messageId":"4E7F313A.2050103@redhat.com","threadId":"28492","inReplyTo":"CAMK1S_joYUKPXDKyomFdbDP4H0UhcwtNQbC89gvNZOTHowYrLw@mail.gmail.com","subject":"Re: Symbolic refs and the git protocol?","fromName":"Avi Kivity","fromEmail":"avi@redhat.com","sentAt":"2011-09-25T13:48:42Z","receivedAt":"2011-09-25T13:48:42Z","isPatch":false,"sender":{"key":"avi@redhat.com","avatar":null},"body":"On 09/25/2011 04:42 PM, Sitaram Chamarty wrote:\n> On Sun, Sep 25, 2011 at 6:47 PM, Avi Kivity wrote:\n> > With the old kernel.org setup, practically the only think I needed to do on\n> > the server itself is the 'git symbolic-ref' command (used to point\n> > refs/heads/linux-next at the correct stream).\n> >\n> > Now it looks like kernel.org will no longer offer shell access. Is it\n> > possible to support symbolic-ref via 'git push'?\n>\n> Can I assume you mean specifically for HEAD, as in 'git symbolic-ref\n> HEAD refs/heads/some-branch'?\n\nNo, I use them for ordinary branches, for example\n\n git symbolic-ref refs/heads/linux-next refs/heads/kvm-updates/3.2\n\nfrom this point on, any update to kvm-updates/3.2 will be reflected in \nthe linux-next ref.\n\n> Although gitolite disables shell access by design, it provides several\n> (optionally installed) features to allow specific shell commands to be\n> executed. One such command is \"set-head\", which does exactly what you\n> ask. You run it like 'ssh git@server set-head reponame.git\n> refs/heads/foo' and it ends up running 'git symbolic-ref HEAD\n> refs/heads/foo' in the repo.\n>\n> I realise that does not answer \"can it be done via git push\" but I\n> thought it might help...\n\nWell, if set-head can be extended a bit, it would suit me perfectly.\n\n-- \nerror compiling committee.c: too many arguments to function\n"},{"id":"176171","messageId":"CAMK1S_g1Co8vogBuObQVsr+nT09urYs+qifJn1X+eGrkgUQZCA@mail.gmail.com","threadId":"28492","inReplyTo":"4E7F313A.2050103@redhat.com","subject":"Re: Symbolic refs and the git protocol?","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-09-25T14:10:11Z","receivedAt":"2011-09-25T14:10:11Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Sun, Sep 25, 2011 at 7:18 PM, Avi Kivity wrote:\n> On 09/25/2011 04:42 PM, Sitaram Chamarty wrote:\n>>\n>> On Sun, Sep 25, 2011 at 6:47 PM, Avi Kivity  wrote:\n>> >  With the old kernel.org setup, practically the only think I needed to\n>> > do on\n>> >  the server itself is the 'git symbolic-ref' command (used to point\n>> >  refs/heads/linux-next at the correct stream).\n>> >\n>> >  Now it looks like kernel.org will no longer offer shell access.  Is it\n>> >  possible to support symbolic-ref via 'git push'?\n>>\n>> Can I assume you mean specifically for HEAD, as in 'git symbolic-ref\n>> HEAD refs/heads/some-branch'?\n>\n> No, I use them for ordinary branches, for example\n>\n>  git symbolic-ref refs/heads/linux-next refs/heads/kvm-updates/3.2\n>\n> from this point on, any update to kvm-updates/3.2 will be reflected in the\n> linux-next ref.\n>\n>> Although gitolite disables shell access by design, it provides several\n>> (optionally installed) features to allow specific shell commands to be\n>> executed.  One such command is \"set-head\", which does exactly what you\n>> ask.  You run it like 'ssh git@server set-head reponame.git\n>> refs/heads/foo' and it ends up running 'git symbolic-ref HEAD\n>> refs/heads/foo' in the repo.\n>>\n>> I realise that does not answer \"can it be done via git push\" but I\n>> thought it might help...\n>\n> Well, if set-head can be extended a bit, it would suit me perfectly.\n\nno reason it can't; shorn of all the argument/access checking, it's a\nvery simple shell script\n\n-- \nSitaram\n"},{"id":"176177","messageId":"20110925185004.GA12781@LK-Perkele-VI.localdomain","threadId":"28492","inReplyTo":"4E7F29EB.8000800@redhat.com","subject":"Re: Symbolic refs and the git protocol?","fromName":"Ilari Liusvaara","fromEmail":"ilari.liusvaara@elisanet.fi","sentAt":"2011-09-25T18:50:04Z","receivedAt":"2011-09-25T18:50:04Z","isPatch":false,"sender":{"key":"ilari.liusvaara@elisanet.fi","avatar":null},"body":"On Sun, Sep 25, 2011 at 04:17:31PM +0300, Avi Kivity wrote:\n>\n> Now it looks like kernel.org will no longer offer shell access. Is\n> it possible to support symbolic-ref via 'git push'?\n\nAFAIK, no, it isn't.\n\n-Ilari\n"},{"id":"176210","messageId":"CAMK1S_gfw4WUdhdCzFMNbJXJP7762tp62fpmQ_-qJLwvD1hR-A@mail.gmail.com","threadId":"28492","inReplyTo":"CAMK1S_g1Co8vogBuObQVsr+nT09urYs+qifJn1X+eGrkgUQZCA@mail.gmail.com","subject":"Re: Symbolic refs and the git protocol?","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-09-26T14:23:24Z","receivedAt":"2011-09-26T14:23:24Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On Sun, Sep 25, 2011 at 7:40 PM, Sitaram Chamarty wrote:\n> On Sun, Sep 25, 2011 at 7:18 PM, Avi Kivity wrote:\n>> On 09/25/2011 04:42 PM, Sitaram Chamarty wrote:\n>>>\n>>> On Sun, Sep 25, 2011 at 6:47 PM, Avi Kivity  wrote:\n>>> >  With the old kernel.org setup, practically the only think I needed to\n>>> > do on\n>>> >  the server itself is the 'git symbolic-ref' command (used to point\n>>> >  refs/heads/linux-next at the correct stream).\n>>> >\n>>> >  Now it looks like kernel.org will no longer offer shell access.  Is it\n>>> >  possible to support symbolic-ref via 'git push'?\n>>>\n>>> Can I assume you mean specifically for HEAD, as in 'git symbolic-ref\n>>> HEAD refs/heads/some-branch'?\n>>\n>> No, I use them for ordinary branches, for example\n>>\n>>  git symbolic-ref refs/heads/linux-next refs/heads/kvm-updates/3.2\n>>\n>> from this point on, any update to kvm-updates/3.2 will be reflected in the\n>> linux-next ref.\n>>\n>>> Although gitolite disables shell access by design, it provides several\n>>> (optionally installed) features to allow specific shell commands to be\n>>> executed.  One such command is \"set-head\", which does exactly what you\n>>> ask.  You run it like 'ssh git@server set-head reponame.git\n>>> refs/heads/foo' and it ends up running 'git symbolic-ref HEAD\n>>> refs/heads/foo' in the repo.\n>>>\n>>> I realise that does not answer \"can it be done via git push\" but I\n>>> thought it might help...\n>>\n>> Well, if set-head can be extended a bit, it would suit me perfectly.\n>\n> no reason it can't; shorn of all the argument/access checking, it's a\n> very simple shell script\n\nDone.\n\nhttps://github.com/sitaramc/gitolite/commit/a2fd597c51a086a0f7298c1641337faa0f296a62\n\nI like this much better actually, so thanks for the idea.\n"},{"id":"176212","messageId":"4E8090E5.4030809@redhat.com","threadId":"28492","inReplyTo":"CAMK1S_gfw4WUdhdCzFMNbJXJP7762tp62fpmQ_-qJLwvD1hR-A@mail.gmail.com","subject":"Re: Symbolic refs and the git protocol?","fromName":"Avi Kivity","fromEmail":"avi@redhat.com","sentAt":"2011-09-26T14:49:09Z","receivedAt":"2011-09-26T14:49:09Z","isPatch":false,"sender":{"key":"avi@redhat.com","avatar":null},"body":"On 09/26/2011 05:23 PM, Sitaram Chamarty wrote:\n> On Sun, Sep 25, 2011 at 7:40 PM, Sitaram Chamarty wrote:\n> > On Sun, Sep 25, 2011 at 7:18 PM, Avi Kivity wrote:\n> >> On 09/25/2011 04:42 PM, Sitaram Chamarty wrote:\n> >>>\n> >>> On Sun, Sep 25, 2011 at 6:47 PM, Avi Kivity wrote:\n> >>> > With the old kernel.org setup, practically the only think I needed to\n> >>> > do on\n> >>> > the server itself is the 'git symbolic-ref' command (used to point\n> >>> > refs/heads/linux-next at the correct stream).\n> >>> >\n> >>> > Now it looks like kernel.org will no longer offer shell access. Is it\n> >>> > possible to support symbolic-ref via 'git push'?\n> >>>\n> >>> Can I assume you mean specifically for HEAD, as in 'git symbolic-ref\n> >>> HEAD refs/heads/some-branch'?\n> >>\n> >> No, I use them for ordinary branches, for example\n> >>\n> >> git symbolic-ref refs/heads/linux-next refs/heads/kvm-updates/3.2\n> >>\n> >> from this point on, any update to kvm-updates/3.2 will be reflected in the\n> >> linux-next ref.\n> >>\n> >>> Although gitolite disables shell access by design, it provides several\n> >>> (optionally installed) features to allow specific shell commands to be\n> >>> executed. One such command is \"set-head\", which does exactly what you\n> >>> ask. You run it like 'ssh git@server set-head reponame.git\n> >>> refs/heads/foo' and it ends up running 'git symbolic-ref HEAD\n> >>> refs/heads/foo' in the repo.\n> >>>\n> >>> I realise that does not answer \"can it be done via git push\" but I\n> >>> thought it might help...\n> >>\n> >> Well, if set-head can be extended a bit, it would suit me perfectly.\n> >\n> > no reason it can't; shorn of all the argument/access checking, it's a\n> > very simple shell script\n>\n> Done.\n>\n> https://github.com/sitaramc/gitolite/commit/a2fd597c51a086a0f7298c1641337faa0f296a62\n>\n> I like this much better actually, so thanks for the idea.\n\nThanks very much for the rapid response and update!\n\nJohn, can we get this into the new kernel.org infrastructure?\n\n-- \nerror compiling committee.c: too many arguments to function\n"}]}