From: Tomas Carnecky <tom@dbservice.com>
To: Mahesh Vaidya <forvaidya@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: push instead of
Date: Fri, 30 Apr 2010 19:24:01 +0200 [thread overview]
Message-ID: <4BDB1231.9090600@dbservice.com> (raw)
In-Reply-To: <z2gb42431c81004300256ke7248f40y7bce060d52cfa943@mail.gmail.com>
On 4/30/10 11:56 AM, Mahesh Vaidya wrote:
> I am facing problem at pushInsteadIOf. I would like pull from
> "pullhost" and push to "pushhost" as my pullhost as pre-receive
> trigger which not accepting pushes.
>
> However when I do git push it still hits pull host. I have following config.
>
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = gitosis@pull_host:repos.git
pushurl = gitosis@PUSH_host:repos.git
tom
next prev parent reply other threads:[~2010-04-30 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 9:56 push instead of Mahesh Vaidya
2010-04-30 17:24 ` Tomas Carnecky [this message]
2010-04-30 18:24 ` Mahesh Vaidya
2010-04-30 22:11 ` Tomas Carnecky
2010-04-30 23:59 ` Jay Soffian
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=4BDB1231.9090600@dbservice.com \
--to=tom@dbservice.com \
--cc=forvaidya@gmail.com \
--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).