From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: Git mirrors Date: Fri, 07 Oct 2011 02:36:54 -0500 Message-ID: References: <87zkhdqo3d.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1317973027 2516 80.91.229.12 (7 Oct 2011 07:37:07 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 7 Oct 2011 07:37:07 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 07 09:37:03 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RC4zO-0004zB-RE for ged-emacs-devel@m.gmane.org; Fri, 07 Oct 2011 09:37:02 +0200 Original-Received: from localhost ([::1]:49952 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RC4zO-0006CX-26 for ged-emacs-devel@m.gmane.org; Fri, 07 Oct 2011 03:37:02 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:44719) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RC4zM-0006CO-Cx for emacs-devel@gnu.org; Fri, 07 Oct 2011 03:37:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RC4zK-0006ga-Sz for emacs-devel@gnu.org; Fri, 07 Oct 2011 03:37:00 -0400 Original-Received: from mail-iy0-f169.google.com ([209.85.210.169]:41081) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RC4zK-0006gU-Ph for emacs-devel@gnu.org; Fri, 07 Oct 2011 03:36:58 -0400 Original-Received: by iaen33 with SMTP id n33so5253016iae.0 for ; Fri, 07 Oct 2011 00:36:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=to:cc:subject:references:from:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=fx2jtOzCyd1k1T3YwcO11g1KnvRWYrBZ0oNxNSn9rNI=; b=FD1Gz2aYXvB3aqqkzCuCQqCwqNoG1sDGMBU8cUjmRUzgP1QXUxCk764KZ7RDkW7WfQ NHlZVkfyDMZqXZAs0zSVTgGrBdCZYagC9Vq1Zu0JN4ifUAUt5ycWART/7qjgQ6rihy8V +q0jBcE9OgTMmxnllG+j9d8G6HIbx8rBTTGAQ= Original-Received: by 10.42.172.194 with SMTP id o2mr10487092icz.15.1317973017702; Fri, 07 Oct 2011 00:36:57 -0700 (PDT) Original-Received: from vulcan.localhost (c-98-215-105-167.hsd1.il.comcast.net. [98.215.105.167]) by mx.google.com with ESMTPS id g16sm17847498ibs.8.2011.10.07.00.36.56 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 07 Oct 2011 00:36:57 -0700 (PDT) Original-Received: by vulcan.localhost (Postfix, from userid 501) id 8B1F25037FEA; Fri, 7 Oct 2011 02:36:54 -0500 (CDT) In-Reply-To: <87zkhdqo3d.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Fri, 07 Oct 2011 16:04:38 +0900") User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.3 (darwin) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.210.169 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:144670 Archived-At: >>>>> Stephen J Turnbull writes: > (If you haven't already done so) May I suggest that you make the bzr > revision id available somehow for every revision (probably use of "git > notes" would be best)? If the canonical git mirror always makes the revid > available, you can ask reporters to fish it out. Somebody[tm] will quickly > write a command to extract it and do something vc.el-y with it (eg, bzr > diff, bzr revert). And of course report-emacs-bug can be trained to DTRT > here. I will see what can be done. Due to the nature of Git, my own Bazaar mirror has entirely different commit ids than what Savannah has. This can be dealt with in the following ways: 1. Start a new mirror, telling people to look there if they wish to follow Git. 2. Merge the current Git mirror into mine. This has the downside that every commit before that merge would be duplicated. 3. Overwrite the current mirror with my own. This will wreak havoc throughout the realm, as everyone on their next pull would merge their own histories with the new mirror, thus duplicating each commit not on the server, but on every client machine who had cloned before now. > Note that you *don't* need to do this immediately for past revisions. If > some bzr-lover wants them, because git notes are ahistorical, they can be > added later by sis (a Sufficiently Intelligent Script), and in any case > they'll rapidly become obsolete. Notes can be useful, but they don't propagate through a clone. What I do have is an upstream-git-map file, which I can make available over HTTP. Simply grep'ing this file will correlate BZR ids to Git commit hashes, and vice-versa. John