From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Yates Newsgroups: gmane.emacs.devel Subject: Re: Moving to bzr? Date: Wed, 21 Jan 2009 18:33:08 -0500 Message-ID: <3f14737c0901211533p87ee668wce75d76143c40893@mail.gmail.com> References: <87mye6xnsr.fsf@xemacs.org> <87y6xpvyz6.fsf@xemacs.org> <87zli4jcc4.fsf@workhorse.earlhome> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1232580866 2128 80.91.229.12 (21 Jan 2009 23:34:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 21 Jan 2009 23:34:26 +0000 (UTC) Cc: Juanma Barranquero , Eli Zaretskii , "Stephen J. Turnbull" , Jason Earl , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 22 00:35:38 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 1LPmbh-0006LQ-J7 for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2009 00:35:37 +0100 Original-Received: from localhost ([127.0.0.1]:43965 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPmaQ-0007Wb-AP for ged-emacs-devel@m.gmane.org; Wed, 21 Jan 2009 18:34:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LPmZO-0007ML-TJ for emacs-devel@gnu.org; Wed, 21 Jan 2009 18:33:14 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LPmZN-0007Ld-HT for emacs-devel@gnu.org; Wed, 21 Jan 2009 18:33:14 -0500 Original-Received: from [199.232.76.173] (port=55753 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPmZN-0007LU-6d for emacs-devel@gnu.org; Wed, 21 Jan 2009 18:33:13 -0500 Original-Received: from wf-out-1314.google.com ([209.85.200.174]:10975) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LPmZK-0008Nq-9H; Wed, 21 Jan 2009 18:33:10 -0500 Original-Received: by wf-out-1314.google.com with SMTP id 28so3877980wfc.24 for ; Wed, 21 Jan 2009 15:33:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=Lmi8yAQ31hDCYhAiVQzgHGcMBjKR8lr/EGYAvCgzObM=; b=iF9yuBn5i5K5s5ehCZIuM7fpUCIbxrS2MYoj34DY5PsocQ7A+5773Pn+DLOiJZRdo1 VPbGTKJ1bAxyotgoBrzGkVJz5GNVM+JYo8RgqrBRe8D2YBRazoZ+hK7j8xH1tag7JZma wFSxjQ/eRSrHAdAV3J1wiMRoqdxGRKmen+IRY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=cFmEw29kUQmyFvYvcswGCDO15moDWyP8BxUihpeTheCn9eDaKrYczjBzlndCa5XXh6 919FyPYIGkfVmUlo1k8ydGSqt9z4tGjDnY2CxQjmuug0Cvj0mgGYxi95GLVBkaAdaMme G97AfD/C4KGm4apXrcdDIdsz7ZfqG/kvnvwHk= Original-Received: by 10.142.134.17 with SMTP id h17mr236332wfd.228.1232580788247; Wed, 21 Jan 2009 15:33:08 -0800 (PST) In-Reply-To: X-Google-Sender-Auth: 4df84891dcdf0e8f 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:108062 Archived-At: Jason Earl wrote: >> I also think that it might be a good idea to wait for some of the >> current repository format changes to land. The new format in 1.9 is a >> definite improvement, but I think that it would be wise to at least wait >> until one of the rich-root variants becomes the default format. Stefan Monnier replied: >Based on the last discussion around rich-root becoming the default, I'd >say "don't hold your breath". Rich-root support is available today. Any new bzr format will always be rolled out accompanied by a rich-root variant. That defaulting to rich-root may take bzr some time does that preclude the emacs project from initializing its master repository as rich-root? After that would not rich-rootiness simply propagate to new branches? /john