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 17:46:04 -0500 [thread overview]
Message-ID: <9e4733910711111446u3e19be7ch90cf79f1d3efc3ef@mail.gmail.com> (raw)
In-Reply-To: <A7871D5B-9E05-4F9B-92AC-B74ECF35460B@zib.de>
On 11/11/07, Steffen Prohaska <prohaska@zib.de> wrote:
>
> On Nov 11, 2007, at 10:20 PM, Jon Smirl wrote:
>
> > 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.
>
> How about the following (untested sequence)
>
> mkdir linux-2.6
> cd linux-2.6
> git init
> git remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/
> torvalds/linux-2.6.git
> git remote add origin ssh://jonsmirl1@git.digispeaker.com/~/
> mpc5200b.git
> git fetch linus
> git fetch origin
> git checkout -b master origin/master
>
> The general idea should be correct. You have a non-standard
> setup, so avoid git-clone.
What should I do to standardize the setup so that 'clone/pull' will
work on it? I created a master branch. I gave up on fighting with
gitweb and no branch named master.
I'd like to do this, but I can't figure out how.
git clone linus
move origin to digispeaker
git pull
There doesn't seem to be a simple way to redirect the origin.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-11-11 22:46 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
2007-11-11 22:01 ` Steffen Prohaska
2007-11-11 22:46 ` Jon Smirl [this message]
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=9e4733910711111446u3e19be7ch90cf79f1d3efc3ef@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).