From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: Moving to bzr? Date: Tue, 6 Jan 2009 23:14:20 +0100 Message-ID: References: <871vviif6s.fsf@xemacs.org> <87mye6xnsr.fsf@xemacs.org> <87y6xpvyz6.fsf@xemacs.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1231280111 1480 80.91.229.12 (6 Jan 2009 22:15:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 6 Jan 2009 22:15:11 +0000 (UTC) Cc: Eli Zaretskii , "Stephen J. Turnbull" , emacs-devel@gnu.org To: "Stefan Monnier" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 06 23:16:22 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LKKDl-0004D8-Bp for ged-emacs-devel@m.gmane.org; Tue, 06 Jan 2009 23:16:21 +0100 Original-Received: from localhost ([127.0.0.1]:44238 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LKKCV-0005aX-U7 for ged-emacs-devel@m.gmane.org; Tue, 06 Jan 2009 17:15:03 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LKKBr-0005CZ-VK for emacs-devel@gnu.org; Tue, 06 Jan 2009 17:14:24 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LKKBq-0005BD-US for emacs-devel@gnu.org; Tue, 06 Jan 2009 17:14:23 -0500 Original-Received: from [199.232.76.173] (port=36392 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LKKBq-0005Ay-N0 for emacs-devel@gnu.org; Tue, 06 Jan 2009 17:14:22 -0500 Original-Received: from an-out-0708.google.com ([209.85.132.248]:4457) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LKKBp-0008T1-1y; Tue, 06 Jan 2009 17:14:21 -0500 Original-Received: by an-out-0708.google.com with SMTP id c38so2610377ana.21 for ; Tue, 06 Jan 2009 14:14:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=z1wsx7jwvDrn0te2Gs2hzDEfVs2U1vBl2qHp3KXrjms=; b=yGZesRtNeGepoaDgjDNpfh+OYVRzHxU12YFzz5I1jSRNcrYUoitGrKDJGWt57e8EOK HlF1otAJpjyKZCQBcYWA8t3DCERp/YVsLey/kRQHyHhrkrcC2fDsqZeSyG4dC/h/P1tV /gFnXuDmuW7fesgPPUivFqcKIuDo26BEFyTr8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=G/wY7wcIHBb0FkPNFQiSW6Lg0Aq6CYzgzxD2oiw0PtSjaT8ALSRPQXoKH9lrgyh89L +L5q2ge8xt+JXhYHjGa9r7b3O5JzfN4bb3gMGjVt+9BnP5eGU06hUMXmD2CRBDK3y5LJ 9tLNShWcEtp+Mxg7F9qasd9J4m0jdkcPdr1Ws= Original-Received: by 10.100.111.11 with SMTP id j11mr12057736anc.15.1231280060601; Tue, 06 Jan 2009 14:14:20 -0800 (PST) Original-Received: by 10.100.252.15 with HTTP; Tue, 6 Jan 2009 14:14:20 -0800 (PST) In-Reply-To: Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107670 Archived-At: On Tue, Jan 6, 2009 at 23:03, Stefan Monnier wrote: > I think I wrote this a few weeks ago, but here it goes again: Sorry, I surely missed it. > From that point of view, I think we can switch any time now. Assuming we had a good repository, how would the change go? Would the bzr be the main repository, or just a mirror for some time? Will we maintain the current workflow and policies, where every developer has full write access? Will we add some kind of review process? Is Savannah ready for the change? Is there something developers should do to switch, other than just installing bzr and cloning the repository? Some of these questions will need answered, IMO. > The main remaining problem is to come up with a good Bzr repository: the > one I've been using (maintained by Jason Earl) has some missing tags, > and lacks merge history as well as file-move information. [...] > I.e. we're just waiting for a good Bzr repository with complete tag > data, and with as much merge history as we can get, Well, is there anyone knowledgeable enough in CVS, bzr and Arch to lead the process? Juanma