git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Local branch to remote branch translation

From
Jon Smirl <jonsmirl@gmail.com>
Date
Nov 12, 2007, 13:53 UTC
Message-ID
<9e4733910711120553r6b7e887eke3978c04b2f0b0c4@mail.gmail.com>
In-Reply-To
<1310ED7B-9DA5-47EC-8523-F609A1866384@zib.de>
On 11/12/07, Steffen Prohaska <prohaska@zib.de> wrote:
Show 61 quoted lines
>
> On Nov 11, 2007, at 11:46 PM, Jon Smirl wrote:
>
> > 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?
>
> Pull should work after you checked out origin/master. Pull should
> fetch from origin and merge to local master.
>
> But I don't see a way how you could use clone for your setup.
>
>
> > I created a master branch. I gave up on fighting with
> > gitweb and no branch named master.
>
> I don't understand your comment about gitweb.

At http://git.digispeaker.com/ The short log, log, tree links won't work unless master exists. Once master is there, everything works.

Show 16 quoted lines
>
>
> > 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.
>
> I don't know a simple way.
>
>         Steffen
>
>
>
-- 
Jon Smirl
jonsmirl@gmail.com
Previous: Steffen Prohaska
Message 10 of 10 in “Local branch to remote branch translation”
  1. Jon SmirlNov 11, 2007
  2. Jon SmirlNov 11, 2007
  3. Steffen ProhaskaNov 11, 2007
  4. Jon SmirlNov 11, 2007
  5. Steffen ProhaskaNov 11, 2007
  6. Jon SmirlNov 11, 2007
  7. Steffen ProhaskaNov 11, 2007
  8. Jon SmirlNov 11, 2007
  9. Steffen ProhaskaNov 12, 2007
  10. Jon SmirlNov 12, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.