From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Cloning from kernel.org, then switching to another repo
Date: Mon, 12 Nov 2007 11:22:41 -0500 [thread overview]
Message-ID: <9e4733910711120822x18019fe6v40eb8ee0e48282dd@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711121613570.4362@racer.site>
On 11/12/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Mon, 12 Nov 2007, Jon Smirl wrote:
>
> > On 11/12/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> >
> > > On Mon, 12 Nov 2007, Jon Smirl wrote:
> > >
> > > > git clone linus
> > > > move origin to digispeaker.git
> > >
> > > AKA "git config remote.origin.url <your-digispeaker-url-here>"
> >
> > There is more to this:
>
> You must be hiding something.
>
> > jonsmirl@terra:~/foo$ git clone
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git ds
> > clone.....
>
> This sets up branch.master.{remote,merge} to {origin,master}.
>
> > jonsmirl@terra:~/foo/ds$ git config remote.origin.url
> > http://git.digispeaker.com/projects/digispeaker-kernel.git
>
> This does not change that setting.
It edited origin:[remote "origin"]
url = http://git.digispeaker.com/projects/digispeaker-kernel.git
fetch = +refs/heads/*:refs/remotes/origin/*
> > jonsmirl@terra:~/foo/ds$ git pull
> > You asked me to pull without telling me which branch you
> > want to merge with, and 'branch.master.merge' in
> > your configuration file does not tell me either. Please
> > name which branch you want to merge on the command line and
> > try again (e.g. 'git pull <repository> <refspec>').
> > See git-pull(1) for details on the refspec.
>
> And this does not come up here.
>
> Maybe you don't have a master branch on digispeaker.
At digispeaker remote repo:
[daedalus]$ git branch
m24
m25
m26
m28
m29
* master
[daedalus]$
gitweb is at:
git.digispeaker.com
[daedalus]$ cd refs
[daedalus]$ find
.
./heads
./heads/m24
./heads/m25
./heads/m26
./heads/m28
./heads/m29
./heads/master
./tags
[daedalus]$
>
> Ciao,
> Dscho
>
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-11-12 16:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 13:57 Cloning from kernel.org, then switching to another repo Jon Smirl
2007-11-12 14:13 ` Johannes Schindelin
2007-11-12 15:36 ` Jon Smirl
2007-11-12 16:16 ` Johannes Schindelin
2007-11-12 16:22 ` Jon Smirl [this message]
2007-11-12 16:36 ` Johannes Schindelin
2007-11-12 17:21 ` Jon Smirl
2007-11-12 17:28 ` Jon Smirl
2007-11-13 4:14 ` Jeff King
2007-11-13 4:20 ` Jeff King
2007-11-13 4:30 ` Jon Smirl
2007-11-13 4:48 ` Jeff King
2007-11-13 9:52 ` Matthieu Moy
2007-11-13 19:13 ` Junio C Hamano
2007-11-13 19:27 ` Jon Smirl
2007-11-13 19:33 ` Jakub Narebski
2007-11-12 20:31 ` Linus Torvalds
2007-11-12 20:42 ` Johannes Schindelin
2007-11-12 20:54 ` Jon Smirl
2007-11-13 4:23 ` Jeff King
2007-11-13 4:33 ` Jon Smirl
2007-11-12 20:51 ` 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
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=9e4733910711120822x18019fe6v40eb8ee0e48282dd@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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.
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).