From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Locks on the Bzr repository Date: Sun, 22 Aug 2010 20:25:49 +0900 Message-ID: <87eidq7ute.fsf@uwakimon.sk.tsukuba.ac.jp> References: <4C6D56DB.7040703@swipnet.se> <4C6D8EC5.7040901@swipnet.se> <4C6E1F0A.7070506@swipnet.se> <837hjlr78p.fsf@gnu.org> <87zkwhtws5.fsf@uwakimon.sk.tsukuba.ac.jp> <83tymppj62.fsf@gnu.org> <871v9t8klf.fsf@uwakimon.sk.tsukuba.ac.jp> <83lj81pazq.fsf@gnu.org> <83aaogpcbu.fsf@gnu.org> <87vd737pxd.fsf@uwakimon.sk.tsukuba.ac.jp> <83pqxboi38.fsf@gnu.org> <19568.59349.718000.978281@gargle.gargle.HOWL> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1282476555 32641 80.91.229.12 (22 Aug 2010 11:29:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 22 Aug 2010 11:29:15 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Uday S Reddy Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 22 13:29:14 2010 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.69) (envelope-from ) id 1On8jh-0005zB-TV for ged-emacs-devel@m.gmane.org; Sun, 22 Aug 2010 13:29:14 +0200 Original-Received: from localhost ([127.0.0.1]:38070 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1On8jh-0001Qg-3x for ged-emacs-devel@m.gmane.org; Sun, 22 Aug 2010 07:29:13 -0400 Original-Received: from [140.186.70.92] (port=57220 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1On8jY-0001Oh-Ub for emacs-devel@gnu.org; Sun, 22 Aug 2010 07:29:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1On8jX-00018t-On for emacs-devel@gnu.org; Sun, 22 Aug 2010 07:29:04 -0400 Original-Received: from imss12.cc.tsukuba.ac.jp ([130.158.254.161]:55189) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1On8jX-00018n-8p for emacs-devel@gnu.org; Sun, 22 Aug 2010 07:29:03 -0400 Original-Received: from imss12.cc.tsukuba.ac.jp (imss12.cc.tsukuba.ac.jp [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 1665FF4003; Sun, 22 Aug 2010 20:29:01 +0900 (JST) Original-Received: from mgmt2.sk.tsukuba.ac.jp (unknown [130.158.97.224]) by imss12.cc.tsukuba.ac.jp (Postfix) with ESMTP id 06123F4002; Sun, 22 Aug 2010 20:29:01 +0900 (JST) Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 01129970311; Sun, 22 Aug 2010 20:29:01 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id E81E31A2C38; Sun, 22 Aug 2010 20:25:49 +0900 (JST) In-Reply-To: <19568.59349.718000.978281@gargle.gargle.HOWL> X-Mailer: VM undefined under 21.5 (beta29) "garbanzo" ed3b274cc037 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:129026 Archived-At: Uday S Reddy writes: > If Bazaar is a "gnu project", can FSF lean on them to produce a > proper integrated rebase? Unlikely. The FSF won't even "lean" on Savannah to properly support the "official" GNU VCS. I believe that RMS has suggested that if this is "really" a problem for (some) Emacs developers, then the (affected) Emacs developers might want to contribute actively to the Bazaar project. My impression is that the active Bazaar developers are much less opposed to a proper rebase than they once were, but Bazaar itself doesn't need it because of their pqm-based workflow, and the Bazaar developers most interested in this feature are concentrating on other work (ie, they're not that interested). So I think a third-party contribution would receive proper review and some mentoring (mostly focused on winkling the patch through the Bazaar contribution process, but some technical help as well). That's probably the best way. Caveat: you probably won't get "integrated" rebase, but having a robust plugin should be good enough (and fits better with the Bazaar philosophy, both about VCS, and about good development process).