From: Cary Coutant <ccoutant@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>,
GDB Development <gdb@sourceware.org>,
Binutils Development <binutils@sourceware.org>
Subject: Re: git is live
Date: Mon, 28 Oct 2013 22:35:00 -0000 [thread overview]
Message-ID: <CAHACq4qqw4MZznnW7zAnOMW2kHEYRRyymAphoEiY1Of5Qeks8w@mail.gmail.com> (raw)
In-Reply-To: <5266CCDC.6090803@redhat.com>
> Created a fresh clone from scratch:
>
> $ mkdir binutils-gdb
> $ cd binutils-gdb
> $ git clone ssh://sourceware.org/git/binutils-gdb.git src
>
> Then I went back to my old git repo checkout, and added a
> remote pointing to the new local checkout:
>
> $ cd ../../my-old-git-repos-checkout-dir/src
> $ git remote add binutils-gdb /local/path/to/fresh/binutils-gdb/src
> $ git fetch binutils-gdb
>
> Now the same "does the new remote share commits/ancentry"
> process ended in seconds, because it was all local, and git
> started fetching the new repo/remote in a matter of seconds.
>
> So now I did:
>
> $ git remote set-url binutils-gdb ssh://sourceware.org/git/binutils-gdb.git
>
> to reset the remote url back to the real remote url, rather than
> the temporary clone directory.
>
> Voila. Then I did:
>
> $ git fetch binutils-gdb
>
> once more, and that worked as expected.
>
> From there on, I've just been switching to by local
> branches that were based on the old git mirror, and rebased
> them on top of binutils-gdb/master.
I got this far with no problems (thanks!), but my old branches don't
seem to have any common commits with the new binutils-gdb/master. Are
you doing the rebase with an explicit merge-base (e.g., "git branch
new-branch binutils-gdb/master; git rebase --onto new-branch
old-master old-branch")? Or should "git rebase binutils-gdb/master
old-branch" work? (I'm hesitant to try that.)
-cary
next prev parent reply other threads:[~2013-10-28 22:35 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 7:01 Tom Tromey
2013-10-22 7:34 ` Andreas Schwab
2013-10-22 7:54 ` Jonas Maebe
2013-10-22 8:04 ` Mark Kettenis
2013-10-22 15:19 ` Tom Tromey
2013-10-22 15:34 ` Eli Zaretskii
[not found] ` <5266306F.50609@groessler.org>
2013-10-22 8:10 ` Andreas Schwab
2013-10-22 8:21 ` Christian Groessler
2013-10-22 9:59 ` Richard Sandiford
2013-10-22 10:52 ` Fred Cooke
2013-10-22 15:20 ` Tom Tromey
2013-10-22 15:22 ` Fred Cooke
2013-10-22 17:44 ` Pedro Alves
2013-10-22 17:49 ` Jeff Law
2013-10-22 17:51 ` Tom Tromey
2013-10-22 17:57 ` Jeff Law
2013-10-22 18:27 ` Jan-Benedict Glaw
2013-10-22 19:16 ` Andreas Schwab
2013-11-09 18:28 ` Steinar Bang
2013-10-22 15:36 ` Eli Zaretskii
2013-10-22 17:09 ` Jan-Benedict Glaw
2013-10-22 18:41 ` Cary Coutant
2013-10-22 19:07 ` Pedro Alves
2013-10-22 20:41 ` Tom Tromey
2013-10-28 22:35 ` Cary Coutant [this message]
2013-10-29 0:37 ` asmwarrior
2013-10-29 1:53 ` Tom Tromey
2013-10-29 18:12 ` Cary Coutant
2013-10-29 19:25 ` Pedro Alves
2013-10-29 19:39 ` Tom Tromey
2014-01-10 2:56 ` Samuel Bronson
2014-01-10 6:53 ` Eli Zaretskii
2013-10-29 6:33 ` Yao Qi
2013-10-29 19:19 ` Pedro Alves
2013-10-22 18:42 ` Andrew Pinski
2013-10-22 20:42 ` Tom Tromey
2013-10-22 19:19 ` DJ Delorie
2013-10-22 20:43 ` Tom Tromey
2013-10-22 20:46 ` Fred Cooke
2013-10-22 20:50 ` Tom Tromey
2013-10-22 20:57 ` Fred Cooke
2013-10-23 4:58 ` Sergio Durigan Junior
2013-10-23 13:13 ` Tom Tromey
2013-10-23 17:31 ` DJ Delorie
2013-10-23 7:21 ` John Darrington
2013-10-23 13:14 ` Tom Tromey
2013-10-24 5:12 ` John Darrington
2013-10-24 7:30 ` Andreas Schwab
2013-10-24 13:35 ` Paul Smith
2013-10-24 7:36 ` Joel Brobecker
2013-10-24 13:52 ` Tom Tromey
2013-10-24 14:05 ` Tristan Gingold
2013-10-24 14:16 ` Tristan Gingold
2013-10-24 17:05 ` Joel Brobecker
2013-10-24 17:21 ` Tom Tromey
2013-10-24 17:52 ` Joel Brobecker
2013-10-25 3:08 ` Fred Cooke
2013-10-25 12:10 ` Paul Smith
2013-10-25 12:38 ` Joel Brobecker
2013-10-25 17:25 ` John Darrington
2013-10-25 18:27 ` web sites (was: Re: git is live) Paul Smith
2013-10-23 13:21 ` git is live Gary Benson
2013-10-25 13:51 ` Peter Bergner
2013-10-25 13:55 ` Ian Lance Taylor
2013-11-14 10:58 ` Richard Earnshaw
2013-11-14 11:12 ` Joel Brobecker
2013-11-14 16:39 ` Eli Zaretskii
2013-11-14 16:55 ` Ian Lance Taylor
2013-11-14 17:21 ` Eli Zaretskii
2013-11-14 17:25 ` H.J. Lu
2013-11-14 18:15 ` Joel Brobecker
2013-11-14 18:25 ` Andrew Pinski
2013-11-15 7:01 ` Joel Brobecker
2013-10-25 14:09 ` Fred Cooke
2013-10-25 16:40 ` Peter Bergner
2013-10-25 16:49 ` Fred Cooke
2013-10-25 17:12 ` Peter Bergner
2013-10-25 18:01 ` Tom Tromey
2013-10-25 16:01 ` Tom Tromey
2013-10-25 16:48 ` Peter Bergner
2013-10-29 22:23 ` Alan Modra
2013-10-30 0:37 ` Alan Modra
2013-10-30 1:39 ` Tom Tromey
2013-10-30 13:16 ` Tom Tromey
2013-11-04 18:25 ` H.J. Lu
2013-11-05 14:32 ` Tom Tromey
2013-11-05 14:46 ` Tom Tromey
2013-11-06 17:02 ` H.J. Lu
2013-11-06 17:12 ` Will Newton
2013-11-06 17:22 ` Tom Tromey
2013-11-08 17:29 ` H.J. Lu
2013-11-08 18:04 ` H.J. Lu
2013-11-08 18:34 ` Tom Tromey
2013-11-08 18:43 ` H.J. Lu
2013-11-08 19:09 ` Tom Tromey
2013-11-08 19:10 ` Paul Smith
2013-11-08 19:21 ` Tom Tromey
2013-11-08 19:30 ` Andreas Schwab
2013-11-08 19:40 ` Tom Tromey
2013-11-06 19:41 ` Andrew Pinski
2013-11-06 20:01 ` Peter Bergner
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=CAHACq4qqw4MZznnW7zAnOMW2kHEYRRyymAphoEiY1Of5Qeks8w@mail.gmail.com \
--to=ccoutant@google.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@redhat.com \
/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