all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: David Reitter <david.reitter@gmail.com>
Cc: "Eric S. Raymond" <esr@thyrsus.com>, emacs-devel@gnu.org
Subject: Re: Progress on the git repo cleanup
Date: Thu, 06 Mar 2014 21:15:26 +0100	[thread overview]
Message-ID: <87y50n84o1.fsf@igel.home> (raw)
In-Reply-To: <7A33D431-2709-4086-87B4-420C6B39148C@gmail.com> (David Reitter's message of "Thu, 6 Mar 2014 14:53:39 -0500")

David Reitter <david.reitter@gmail.com> writes:

> What is the procedure for those of us that keep a separate branch around, which has multiple (50+) merges from the mainline or Emacs 23, and many private changes?

The minimum requirement is a mapping of every referenced commit in
git.sv.gnu.org/emacs to a commit in the converted repo (it doesn't have
to be one-to-one, but can be many-to-one).  This can then be used to
create a script based on bzr-fastimport to convert private branches.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2014-03-06 20:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 18:21 Progress on the git repo cleanup Eric S. Raymond
2014-03-06 19:53 ` David Reitter
2014-03-06 20:15   ` Andreas Schwab [this message]
2014-03-06 20:24     ` David Reitter
2014-03-06 20:49   ` Eric S. Raymond
2014-03-06 21:34     ` David Reitter
2014-03-06 22:00       ` Eric S. Raymond
2014-03-06 22:13         ` David Reitter
2014-03-06 22:31           ` Andreas Schwab
2014-03-06 22:46           ` Eric S. Raymond
2014-03-12 17:46 ` Andreas Schwab
2014-03-12 17:57   ` Eric S. Raymond
2014-03-12 18:07     ` Karl Fogel
2014-03-12 18:30       ` Eric S. Raymond
2014-03-12 19:38         ` Karl Fogel
2014-03-12 21:18           ` David Kastrup

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=87y50n84o1.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.