From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: bzr repository ready? Date: Mon, 23 Nov 2009 07:07:03 -0500 Message-ID: References: <87zl6vskq0.fsf@red-bean.com> <874op07kb0.fsf@red-bean.com> <87639fr3w7.fsf@red-bean.com> <87vdhfpil2.fsf@red-bean.com> <87einvxy9c.fsf@red-bean.com> <20091118230952.GB908@muc.de> <87my2jw05z.fsf@red-bean.com> <83skc9pbf7.fsf@gnu.org> <87iqd5vw5n.fsf@red-bean.com> <87vdh29lfo.fsf@red-bean.com> <83k4xhoo0n.fsf@gnu.org> <87my2dhlko.fsf@telefonica.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1258978243 28327 80.91.229.12 (23 Nov 2009 12:10:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 23 Nov 2009 12:10:43 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar_Fuentes?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 23 13:10:36 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 1NCXkW-0007C1-PM for ged-emacs-devel@m.gmane.org; Mon, 23 Nov 2009 13:10:33 +0100 Original-Received: from localhost ([127.0.0.1]:40423 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCXkW-0007Yb-50 for ged-emacs-devel@m.gmane.org; Mon, 23 Nov 2009 07:10:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCXhG-0006OX-GC for emacs-devel@gnu.org; Mon, 23 Nov 2009 07:07:10 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCXhB-0006Ma-09 for emacs-devel@gnu.org; Mon, 23 Nov 2009 07:07:09 -0500 Original-Received: from [199.232.76.173] (port=43080 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCXhA-0006MU-N5 for emacs-devel@gnu.org; Mon, 23 Nov 2009 07:07:04 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:58794) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NCXhA-0002Vp-3z for emacs-devel@gnu.org; Mon, 23 Nov 2009 07:07:04 -0500 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1NCXh9-0004Om-PX; Mon, 23 Nov 2009 07:07:03 -0500 In-reply-to: <87my2dhlko.fsf@telefonica.net> (message from =?utf-8?Q?=C3=93scar_Fuentes?= on Mon, 23 Nov 2009 06:11:35 +0100) 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:117576 Archived-At: > From: Óscar_Fuentes > Date: Mon, 23 Nov 2009 06:11:35 +0100 > > Eli Zaretskii writes: > > >> Right now, the only question that's come up that I think belongs in that > >> document is "What should be the standard workflow for Emacs developers > >> in Bazaar?" That's a question we already had a draft answer for, and > >> Stephen Turnbull has since improved it (I'm about to review it). > > > > Except that alternative workflows were mentioned here since then, and > > it is no longer clear to me that the one described on the Wiki is the > > best one. Perhaps we should add a few more there. > > There is no "best-one" workflow. It depends on what kind of work you do, > what's your environment (i.e. connected/disconnected) and even on your > personal preferences. Note that I asked for several alternatives to begin with, because I suspected that much. I was told to go read the EmacsWiki page which describes only one workflow. Now you confirm my guess that more than one workflow should be considered. If others agree that ``there is no "best-one" workflow'', I would suggest that several alternatives be described on the wiki, each one with its advantages and disadvantages. That should give each developer enough information to make up her mind which ones to use, at least initially.