From: Avi Kivity <avi@redhat.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
John Hawley <warthog19@gmail.com>
Subject: Re: Symbolic refs and the git protocol?
Date: Sun, 25 Sep 2011 16:48:42 +0300 [thread overview]
Message-ID: <4E7F313A.2050103@redhat.com> (raw)
In-Reply-To: <CAMK1S_joYUKPXDKyomFdbDP4H0UhcwtNQbC89gvNZOTHowYrLw@mail.gmail.com>
On 09/25/2011 04:42 PM, Sitaram Chamarty wrote:
> On Sun, Sep 25, 2011 at 6:47 PM, Avi Kivity<avi@redhat.com> wrote:
> > With the old kernel.org setup, practically the only think I needed to do on
> > the server itself is the 'git symbolic-ref' command (used to point
> > refs/heads/linux-next at the correct stream).
> >
> > Now it looks like kernel.org will no longer offer shell access. Is it
> > possible to support symbolic-ref via 'git push'?
>
> Can I assume you mean specifically for HEAD, as in 'git symbolic-ref
> HEAD refs/heads/some-branch'?
No, I use them for ordinary branches, for example
git symbolic-ref refs/heads/linux-next refs/heads/kvm-updates/3.2
from this point on, any update to kvm-updates/3.2 will be reflected in
the linux-next ref.
> Although gitolite disables shell access by design, it provides several
> (optionally installed) features to allow specific shell commands to be
> executed. One such command is "set-head", which does exactly what you
> ask. You run it like 'ssh git@server set-head reponame.git
> refs/heads/foo' and it ends up running 'git symbolic-ref HEAD
> refs/heads/foo' in the repo.
>
> I realise that does not answer "can it be done via git push" but I
> thought it might help...
Well, if set-head can be extended a bit, it would suit me perfectly.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-09-25 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 13:17 Symbolic refs and the git protocol? Avi Kivity
2011-09-25 13:42 ` Sitaram Chamarty
2011-09-25 13:48 ` Avi Kivity [this message]
2011-09-25 14:10 ` Sitaram Chamarty
2011-09-26 14:23 ` Sitaram Chamarty
2011-09-26 14:49 ` Avi Kivity
2011-09-25 18:50 ` Ilari Liusvaara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E7F313A.2050103@redhat.com \
--to=avi@redhat.com \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.com \
--cc=warthog19@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.