unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sven Axelsson <sven.axelsson@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs <emacs-devel@gnu.org>
Subject: Re: Switching from old git tree
Date: Fri, 14 Nov 2014 13:35:17 +0100	[thread overview]
Message-ID: <CAP1yDHan488EYJ7ncn5WkvuG15U89KApjVLirjzZENZJ9S1DuA@mail.gmail.com> (raw)
In-Reply-To: <87ioiiotwx.fsf@fencepost.gnu.org>

On 14 November 2014 13:20, David Kastrup <dak@gnu.org> wrote:
> peder@news.klingenberg.no (Peder O. Klingenberg) writes:
>
>> I have been using the old git-mirror for a while.  In there, I have a
>> branch with some local modifications.
>>
>> I understand that I need to check out a fresh tree now after the
>> conversion?  What is the smoothest way of integrating my local branch in
>> this new tree?  I'm a very basic git user, and the only way I can think
>> of is to extract the patches from my old branch and applying them by
>> hand in the new tree.
>
> Using git format-patch and git am, rather than git diff and git apply.
>
>> Is there something else I should be doing instead?
>
> I don't think there is much of an option to do something else.

I suppose you could add your old repo as a local remote to the new one, and
cherry-pick your commits, i.e.:

git remote add old /local/path/to/old
# Fetch the data to your new repo
git fetch old
# Find the commits to pick somehow
git log old/master
# Copy to new repo
git cherry-pick <sha-of-commit>

-- 
Sven Axelsson
++++++++++[>++++++++++>+++++++++++>++++++++++>++++++
>++++<<<<<-]>++++.+.++++.>+++++.>+.<<-.>>+.>++++.<<.
+++.>-.<<++.>>----.<++.>>>++++++.<<<<.>>++++.<----.



  reply	other threads:[~2014-11-14 12:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 11:26 Switching from old git tree Peder O. Klingenberg
2014-11-14 12:20 ` David Kastrup
2014-11-14 12:35   ` Sven Axelsson [this message]
2014-11-14 12:38     ` Sven Axelsson
2014-11-14 13:21     ` Peder O. Klingenberg
2014-11-14 13:53     ` David Kastrup
2014-11-14 14:20       ` Sven Axelsson
2014-11-14 14:54         ` David Kastrup
2014-11-14 15:52         ` Andreas Schwab
2014-11-14 18:29           ` David Caldwell
2014-11-15  8:43       ` Kenneth Raeburn
2014-11-15  8:58         ` Eli Zaretskii
2014-11-15  9:18           ` David Kastrup
2014-11-15  9:55             ` Eli Zaretskii
2014-11-15 18:26             ` Ken Raeburn
2014-11-14 13:29 ` Nicolas Richard

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: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=CAP1yDHan488EYJ7ncn5WkvuG15U89KApjVLirjzZENZJ9S1DuA@mail.gmail.com \
    --to=sven.axelsson@gmail.com \
    --cc=dak@gnu.org \
    --cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).