From: Sitaram Chamarty <sitaramc@gmail.com>
To: Lorenzo Bettini <bettini@dsi.unifi.it>
Cc: git@vger.kernel.org
Subject: Re: pushing remote branches
Date: Sun, 15 Nov 2009 06:15:00 +0530 [thread overview]
Message-ID: <2e24e5b90911141645n59680856ja21f2f3c7063f7c0@mail.gmail.com> (raw)
In-Reply-To: <hdneuv$nc8$2@ger.gmane.org>
Hi Lorenzo,
On Sun, Nov 15, 2009 at 5:07 AM, Lorenzo Bettini <bettini@dsi.unifi.it> wrote:
> url = git://...
> isn't this enough to be able to push the experiments branch?
not normally.
The "git://" protocol is a read-only protocol by default. Since it is
completely unauthenticated, enabling push via git:// is not a good idea in
general.
> url = git@...
This is a shortcut for something like ssh://git@..., which then allows write
also.
next prev parent reply other threads:[~2009-11-15 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 23:37 pushing remote branches Lorenzo Bettini
2009-11-15 0:45 ` Sitaram Chamarty [this message]
2009-11-15 10:21 ` Lorenzo Bettini
2009-11-15 11:04 ` Sitaram Chamarty
2009-11-16 15:27 ` Lorenzo Bettini
2009-11-16 20:05 ` Junio C Hamano
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=2e24e5b90911141645n59680856ja21f2f3c7063f7c0@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=bettini@dsi.unifi.it \
--cc=git@vger.kernel.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).