From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Local branch to remote branch translation
Date: Sun, 11 Nov 2007 13:02:00 -0500 [thread overview]
Message-ID: <9e4733910711111002x2f8cabf7yce263faf7b33bde1@mail.gmail.com> (raw)
In-Reply-To: <9e4733910711110954m3ed3f9adtf19ca15dff61f0@mail.gmail.com>
Is the remote config not correct?
[remote "dreamhost"]
url = ssh://jonsmirl1@git.digispeaker.com/~/mpc5200b.git
fetch = +refs/heads/*:refs/remotes/dreamhost/*
push = +refs/heads/*:refs/remotes/linus/*
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-11-11 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 17:54 Local branch to remote branch translation Jon Smirl
2007-11-11 18:02 ` Jon Smirl [this message]
2007-11-11 18:19 ` Steffen Prohaska
2007-11-11 19:36 ` Jon Smirl
2007-11-11 20:59 ` Steffen Prohaska
2007-11-11 21:20 ` Jon Smirl
2007-11-11 22:01 ` Steffen Prohaska
2007-11-11 22:46 ` Jon Smirl
2007-11-12 6:25 ` Steffen Prohaska
2007-11-12 13:53 ` Jon Smirl
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=9e4733910711111002x2f8cabf7yce263faf7b33bde1@mail.gmail.com \
--to=jonsmirl@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).