From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Git to Bzr - what works? Date: Wed, 15 Aug 2012 16:49:28 -0700 Message-ID: <502C3588.1070707@dancol.org> References: <5029AB54.8020804@dancol.org> <83fw7pjqav.fsf@gnu.org> <877gt1p7s9.fsf@olor.terpri.org> <837gt0kgyk.fsf@gnu.org> <83lihgujim.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig496944D6E9BD8E0D377FC376" X-Trace: ger.gmane.org 1345074619 1846 80.91.229.3 (15 Aug 2012 23:50:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Aug 2012 23:50:19 +0000 (UTC) Cc: Eli Zaretskii , bpt@hcoop.net, Fabian Ezequiel Gallina , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 16 01:50:17 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1T1nLt-0004Q1-Ce for ged-emacs-devel@m.gmane.org; Thu, 16 Aug 2012 01:50:17 +0200 Original-Received: from localhost ([::1]:45621 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1nLr-0008SW-Sh for ged-emacs-devel@m.gmane.org; Wed, 15 Aug 2012 19:50:15 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:49199) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1nLp-0008SQ-Ji for emacs-devel@gnu.org; Wed, 15 Aug 2012 19:50:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T1nLo-0004Mw-KD for emacs-devel@gnu.org; Wed, 15 Aug 2012 19:50:13 -0400 Original-Received: from dancol.org ([96.126.100.184]:35881) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1nLm-0004Lt-KI; Wed, 15 Aug 2012 19:50:10 -0400 Original-Received: from c-76-22-66-162.hsd1.wa.comcast.net ([76.22.66.162] helo=[192.168.1.2]) by dancol.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1T1nLk-0000gk-59; Wed, 15 Aug 2012 16:50:08 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 In-Reply-To: X-Enigmail-Version: 1.4.3 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 96.126.100.184 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:152574 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig496944D6E9BD8E0D377FC376 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 8/15/12 1:45 PM, Stefan Monnier wrote: >> . When you have changes in the bzr repo: >> . "bzr pull" from the git repo to the bzr branch created above >=20 > But his Git repository is the result of a "Bzr->Git" conversion. > So we'd get here a "Bzr->Git->Bzr" conversion. I strongly suspect that= > it is not an identity and that all the revids will be different. I tried cloning a local git mirror (derived from the Savannah git mirorr) using bzr-git. It's even slower than git-bzr. It's used 23 miutes of CPU time and processed 8315 of 122105 records. >> . "bzr merge" to another bzr branch that tracks the Emacs trunk >=20 > If indeed all the revids are different, this will either complain that > there's no common ancestor (best case) or find some distant ancestor an= d > pretty much double the size of the repository with a new copy of the > whole history. >=20 > This said, I don't understand the problem discussed here. > Isn't "git-bzr" bidirectional (i.e. you can "git push" onto the Bzr > repository)? git-bzr would be great if it worked, but it doesn't work for me. After chugging along for about an hour, it fails and complains about a missing committer record. How is the Savannah git mirror being generated? Matching its revids would be the most important part of any bidirectional mirriroing scheme. If Savannah is using git-bzr, I'd like to know the versions of the pieces of software involved and whether the Savannah people made any local modifications. --------------enig496944D6E9BD8E0D377FC376 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlAsNYkACgkQ17c2LVA10VsmKQCgmLfLm+sueoziE0ZW0i6EDvs0 rqQAoINFeMF0/BGFeMWkCKYp5u5Rc/sd =5sxS -----END PGP SIGNATURE----- --------------enig496944D6E9BD8E0D377FC376--