From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Steffen Prohaska" <prohaska@zib.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Local branch to remote branch translation
Date: Sun, 11 Nov 2007 16:20:26 -0500 [thread overview]
Message-ID: <9e4733910711111320u1deafe69r96d64babbb893adf@mail.gmail.com> (raw)
In-Reply-To: <B5C127C0-04B8-4469-B6DD-C8B5335BBA88@zib.de>
On 11/11/07, Steffen Prohaska <prohaska@zib.de> wrote:
> > jonsmirl@terra:~/mpc5200b$ git remote show linus
> > * remote linus
> > URL: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
> > linux-2.6.git
> >
> > How do I push the definition of the linus remote repo?
>
> You can't. Remotes are local to a repository. They cannot be
> "pushed" nor will they be "cloned" or "fetched".
Dreamhost is way slow compared to kernel.org, so it is better to clone
from kernel.org first and then pull from dreamhost. What is the right
sequence of commands so that a new user will end up with a kernel they
can use 'git pull' on to get updates from dreamhost? I'll add these to
the repo description page.
I'm trying this locally and I can't figure out the right sequence of
git command to redirect origin from kernel.org to dreamhost.
Doing this was bad, it messed up my heads.
jonsmirl@terra:~/foo/digispeaker$ git remote rm origin
error: unable to resolve reference refs/remotes/origin/master: No such
file or directory
update-ref -d refs/remotes/origin/master
6e800af233e0bdf108efb7bd23c11ea6fa34cdeb: command returned error: 1
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-11-11 21:20 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
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 [this message]
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=9e4733910711111320u1deafe69r96d64babbb893adf@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.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.
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).