git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Cloning from kernel.org, then switching to another repo
Date: Mon, 12 Nov 2007 15:54:59 -0500	[thread overview]
Message-ID: <9e4733910711121254j5af5dba6k5acdce939936af66@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711122040350.4362@racer.site>

On 11/12/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Mon, 12 Nov 2007, Linus Torvalds wrote:
>
> > On Mon, 12 Nov 2007, Johannes Schindelin wrote:
> > >
> > > On Mon, 12 Nov 2007, Jon Smirl wrote:
> > >
> > > > I'd like to do this sequence, but I can't figure out how without
> > > > editing the config file. There doesn't seem to be a simple command
> > > > to move the origin.
> > > >
> > > > git clone linus
> > > > move origin to digispeaker.git
> > >
> > > AKA "git config remote.origin.url <your-digispeaker-url-here>"
> >
> > I really think people should at least also mention:
> >
> >       "Or just edit your .git/config file by hand"
>
> FWIW I agree.  The intent of git-repo-config (as it was named then) was to
> have a program for _scripts_ to use.
>
> But for some reasons, people on IRC refuse to edit .git/config by hand.
> *sigh*  Will have to relearn giving proper help.

It is eaiser to put
  git config remote.origin.url
http://git.digispeaker.com/projects/digispeaker-kernel.git
in a cookbook web page sequence than say edit the config file by hand.

I added the cookbook sequence to my git project page.
http://git.digispeaker.com/
Without cloning from kernel.org first it takes an hour to clone from
dreamhost, but what do you want for $5/mth. I'll more to a better host
when traffic picks up.

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2007-11-12 20:55 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9e4733910711121254j5af5dba6k5acdce939936af66@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).