unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Miles Bader <miles@gnu.org>
Cc: David Reitter <david.reitter@gmail.com>,
	Ken Raeburn <raeburn@raeburn.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs Development <emacs-devel@gnu.org>
Subject: Re: Bazaar  migration status?
Date: Tue, 21 Jul 2009 10:19:38 +0200	[thread overview]
Message-ID: <m31voaih2d.fsf@hase.home> (raw)
In-Reply-To: <87skgrj8z6.fsf@catnip.gol.com> (Miles Bader's message of "Tue, 21 Jul 2009 07:16:45 +0900")

Miles Bader <miles@gnu.org> writes:

> [Another problem is that even if another syncing tool is available,
> I'm not sure what changing to another source-VCS/tool means for the
> existing history in git...]

Most likely the history will come out different if you recreate the git
tree based on the bzr tree, but that's not a big problem.  If you
maintain any local changes on top of the old git tree just rebase them
on top of the new tree.

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."




  parent reply	other threads:[~2009-07-21  8:19 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 12:41 Bazaar migration status? joakim
2009-07-17 15:50 ` Stefan Monnier
2009-07-17 17:06   ` joakim
2009-07-17 17:56     ` Stefan Monnier
2009-07-19 22:55       ` Daniel Clemente
2009-07-29 16:43         ` Karl Fogel
2009-07-17 18:37     ` Chong Yidong
2009-07-19  6:50       ` Karl Fogel
2009-07-19  9:35         ` joakim
2009-07-19 10:27         ` Ken Raeburn
2009-07-20 13:35           ` Stefan Monnier
2009-07-20 13:55             ` David Reitter
2009-07-20 17:58               ` Stefan Monnier
2009-07-20 22:16                 ` Miles Bader
2009-07-21  0:54                   ` Stefan Monnier
2009-07-21  8:19                   ` Andreas Schwab [this message]
2009-07-21 23:31                     ` Ken Raeburn
2009-07-22  7:19                       ` David Reitter
2009-07-22 21:33                       ` Andreas Schwab
2009-07-22 23:46                         ` Ken Raeburn
2009-07-23  3:49                           ` Stephen J. Turnbull
2009-07-23  5:13                             ` Miles Bader
2009-07-23  5:34                             ` Ken Raeburn
2009-07-23  8:14                               ` Stephen J. Turnbull
2009-07-23 22:06                                 ` Ken Raeburn
2009-07-24  2:43                                   ` Stephen J. Turnbull
2009-07-24  8:45                                     ` Ken Raeburn
2009-07-24 11:13                                       ` Stephen J. Turnbull
2009-07-23  7:53                           ` Andreas Schwab
2009-07-20 22:14       ` Christian Faulhammer

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=m31voaih2d.fsf@hase.home \
    --to=schwab@linux-m68k.org \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=raeburn@raeburn.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).