From: Sitaram Chamarty <sitaramc@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Dun Peal <dunpealer@gmail.com>,
Shawn Pearce <spearce@spearce.org>, Git ML <git@vger.kernel.org>
Subject: Re: Pushing symbolic references to remote repositories?
Date: Sun, 23 Dec 2012 06:40:59 +0530 [thread overview]
Message-ID: <CAMK1S_iKYb0sK+2+H1b7wAPjJGEhJHJk9eK1bsMqxOGKoJuipg@mail.gmail.com> (raw)
In-Reply-To: <7vy5gqq6w8.fsf@alter.siamese.dyndns.org>
On Sat, Dec 22, 2012 at 11:57 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> This is not limited to HEAD, any ref may want to be set up as a symref
>> at a remote repo. For example, I want to set up a symref master ->
>> trunk at a repository I have no shell access to.
>
> That is exactly the "hosting side does not give you an easy way so
> pushing seems to be one plausible but not necessarily has to be the
> only way" case, so it is already covered in the discussion.
Just a minor FYI (and at the risk of tooting my own horn) but if the
hosting side is gitolite, you can.set it up so that any user with
write permissions to the repo can run 'git symbolic-ref' with
arbitrary arguments even though he does not get a shell.
The "-m <reason>" has some constraints because gitolite does not allow
a lot of characters in arguments to remote commands but that's mostly
useless unless you have core.logAllRefUpdates set anyway.
prev parent reply other threads:[~2012-12-23 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 19:53 Pushing symbolic references to remote repositories? Dun Peal
2012-12-21 21:54 ` Shawn Pearce
2012-12-21 23:11 ` Junio C Hamano
2012-12-22 9:26 ` Andreas Schwab
2012-12-22 18:27 ` Junio C Hamano
2012-12-23 1:10 ` Sitaram Chamarty [this message]
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=CAMK1S_iKYb0sK+2+H1b7wAPjJGEhJHJk9eK1bsMqxOGKoJuipg@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=dunpealer@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=schwab@linux-m68k.org \
--cc=spearce@spearce.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).