From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: bzr repository ready? Date: Thu, 29 Jan 2009 15:18:01 -0500 Message-ID: <87d4e57tom.fsf@red-bean.com> References: <87y6xpvyz6.fsf@xemacs.org> <87zli4jcc4.fsf@workhorse.earlhome> <87vdsrjcco.fsf@workhorse.earlhome> <87fxjgb4ud.fsf_-_@red-bean.com> <87eiyy3lag.fsf@notengoamigos.org> <87bpu1451m.fsf@red-bean.com> <874ozs34c6.fsf@notengoamigos.org> <87k58nyih3.fsf@red-bean.com> <87ocxxrjnh.fsf@canonical.com> <874ozp4ld3.fsf@notengoamigos.org> <87ocxrgm4g.fsf@canonical.com> <87ocxqqx1y.fsf@CPU107.opentrends.net> <874ozi7z5u.fsf@red-bean.com> <200901291850.n0TIoa10015665@rodan.ics.uci.edu> Reply-To: Karl Fogel NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1233260302 1463 80.91.229.12 (29 Jan 2009 20:18:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 29 Jan 2009 20:18:22 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 29 21:19:34 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 1LSdMJ-0004ci-Av for ged-emacs-devel@m.gmane.org; Thu, 29 Jan 2009 21:19:31 +0100 Original-Received: from localhost ([127.0.0.1]:51576 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LSdL0-0003QA-Oj for ged-emacs-devel@m.gmane.org; Thu, 29 Jan 2009 15:18:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LSdKw-0003Pv-0S for emacs-devel@gnu.org; Thu, 29 Jan 2009 15:18:06 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LSdKt-0003PH-Rn for emacs-devel@gnu.org; Thu, 29 Jan 2009 15:18:04 -0500 Original-Received: from [199.232.76.173] (port=39985 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LSdKt-0003Oy-MO for emacs-devel@gnu.org; Thu, 29 Jan 2009 15:18:03 -0500 Original-Received: from sanpietro.red-bean.com ([66.146.193.61]:45159) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LSdKt-0001Fa-Fv for emacs-devel@gnu.org; Thu, 29 Jan 2009 15:18:03 -0500 Original-Received: from localhost ([127.0.0.1]:41623 helo=floss ident=kfogel) by sanpietro.red-bean.com with esmtp (Exim 4.69) (envelope-from ) id 1LSdKs-0006yp-4M for emacs-devel@gnu.org; Thu, 29 Jan 2009 14:18:02 -0600 In-Reply-To: <200901291850.n0TIoa10015665@rodan.ics.uci.edu> (Dan Nicolaescu's message of "Thu, 29 Jan 2009 10:50:36 -0800 (PST)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) 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:108375 Archived-At: Dan Nicolaescu writes: > Karl Fogel writes: > > Done: http://www.emacswiki.org/emacs-en/EmacsBzrSwitchover > > Does the current bzr put the version info in the "bzr diff" headers? > Does "bzr log SUBDIR" work now? No, neither of those bugs is fixed yet -- respectively: https://bugs.edge.launchpad.net/bzr/+bug/130588 https://bugs.edge.launchpad.net/bzr/+bug/97715 They're on the bzr developers' radar screen, and I think they will get fixed eventually (I may work on #130588 myself, as soon as I'm done with #306394, but #97715 is likely to be beyond my skills as a bzr dev for some time). Ian Clatworthy has just finished some log improvements (https://lists.ubuntu.com/archives/bazaar/2009q1/052131.html) in performance, and I will be asking him about the 'log SUBDIR' case again. However, I thought we decided these didn't have to block the switchover? It'd obviously be better if they were fixed, especially the latter; I'm just not sure we have to wait. After all, right now we're using a system that doesn't even support renames :-). Very much trying to avoid Error 33, -Karl