From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Nikos Chantziaras <realnc@arcor.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [WIP/RFC] Allow push and fetch urls to be different
Date: Sat, 06 Jun 2009 21:19:34 -0700 [thread overview]
Message-ID: <7vtz2sbrqh.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1244299395-6605-1-git-send-email-git@drmicha.warpmail.net> (Michael J. Gruber's message of "Sat\, 6 Jun 2009 16\:43\:15 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> This introduces a config setting remote.$remotename.pushurl which is
> used for pushes only. If absent remote.$remotename.url is used for
> pushes and fetches as before.
> This is useful, for example, in order to to do passwordless fetches
> (remote update) over git: but pushes over ssh.
>
> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
> ---
> This is a working prototype, but I'd like to rfc about the approach before
> coding further.
As I am guilty for suggesting this, obviously I do not have a problem with
what the patch wants to achieve.
And the change looks simple, straightforward and correct.
> Things that would go in a full series:
> * documentation (man pages, maybe manual)
> * tests
Surely.
> * teach builtin-remote about pushurl
Hmm,... my impression was that "git remote" does not have much support
for the push side. What kind of things are you going to teach?
next prev parent reply other threads:[~2009-06-07 4:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 23:16 Using different protocols for "pull" and "push" Nikos Chantziaras
2009-06-05 0:52 ` Junio C Hamano
2009-06-06 14:43 ` [WIP/RFC] Allow push and fetch urls to be different Michael J Gruber
2009-06-06 14:50 ` Tay Ray Chuan
2009-06-06 17:57 ` Linus Torvalds
2009-06-07 4:19 ` Junio C Hamano [this message]
2009-06-07 9:00 ` Michael J Gruber
2009-06-05 15:03 ` Using different protocols for "pull" and "push" Mike Gaffney
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vtz2sbrqh.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=realnc@arcor.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).