From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs is on Bazaar now. Date: Tue, 29 Dec 2009 05:46:12 +0100 Message-ID: <87oclipeuj.fsf@telefonica.net> References: <87d4206n80.fsf@canonical.com> <87637qhjqu.fsf@red-bean.com> <87fx6urat1.fsf@telefonica.net> <87oclig1qj.fsf@red-bean.com> <87bphir8s4.fsf@telefonica.net> <87zl52o82l.fsf@uwakimon.sk.tsukuba.ac.jp> <87ws06plss.fsf@telefonica.net> <87y6kmo0w7.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1262062022 4162 80.91.229.12 (29 Dec 2009 04:47:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Dec 2009 04:47:02 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 29 05:46:55 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 1NPTyv-0006TM-HI for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 05:46:53 +0100 Original-Received: from localhost ([127.0.0.1]:41022 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPTys-0001Mv-Ft for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2009 23:46:50 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPTyn-0001Me-1N for emacs-devel@gnu.org; Mon, 28 Dec 2009 23:46:45 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPTyi-0001MC-PH for emacs-devel@gnu.org; Mon, 28 Dec 2009 23:46:44 -0500 Original-Received: from [199.232.76.173] (port=39821 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPTyi-0001M1-In for emacs-devel@gnu.org; Mon, 28 Dec 2009 23:46:40 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:53555) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NPTyi-0002We-Dp for emacs-devel@gnu.org; Mon, 28 Dec 2009 23:46:40 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NPTyd-0006Pq-SS for emacs-devel@gnu.org; Tue, 29 Dec 2009 05:46:35 +0100 Original-Received: from 174.red-83-45-255.dynamicip.rima-tde.net ([83.45.255.174]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 29 Dec 2009 05:46:35 +0100 Original-Received: from ofv by 174.red-83-45-255.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 29 Dec 2009 05:46:35 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 49 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 174.red-83-45-255.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (gnu/linux) Cancel-Lock: sha1:HXL/mT9xuW3nS6lpmdWtMYKccjY= 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:118913 Archived-At: "Stephen J. Turnbull" writes: > Óscar Fuentes writes: > > > > And what happens if he actually uses a feature branch? > > > > Then he should use the adequate workflow for a feature branch. > > People DO NOT DO WHAT THEY SHOULD DO. If they did, we wouldn't be > having this discussion. Instead, they look for shortcuts, for > convenience, for the familiar. I think that some people is looking for shortcuts because they find the distributed workflow unnecessarily complex. Either they fail to appreciate the benefits of the added complexity or they think that those benefits are of no value for them. > > > I think there's a lot of room for icky things[tm] to happen if > > > the bzr-update-and-work-on-trunk discipline is mixed with the > > > push-through-a-dedicated-trunk-mirror-branch discipline. > > > > Can you describe some of those icky things? > > No. If I could describe them, I wouldn't be so adamant about a > SINGLE, fairly simple, flexible, socially adapted workflow that works > for almost everybody. I'd figure out a workflow that is more adapted > to existing Emacs usage, with a straightforward upgrade path to "full > tilt boogie" exploitation of advanced DVCS features. Wouldn't you? > > Why do I expect them? Feel free to review the "how do I get myself > out of here" threads on any of the DVCS user lists if you must have > examples. There are plenty on bazaar@canonical.com. In short, there are "icky things" that you can't describe but are extensively discussed on the mailing lists. Oh well. As said on the past, my description of the centralized way is targeted to *reduce* the problems *some* emacs hackers can experience on the transition to bzr, and allow them to keep doing the really important thing: keep contributing. You insist on that having the simpler workflow documented actually creates problems, but so far failed to mention a single serious issue with it. Personally, if I were a hacker doing quick contributions to emacs (the sort of thing that ends on one single commit), I would use the centralized workflow. -- Óscar