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: Fri, 20 Nov 2009 15:34:36 +0200 Message-ID: <83skc9pbf7.fsf@gnu.org> 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> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1258724090 4503 80.91.229.12 (20 Nov 2009 13:34:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 20 Nov 2009 13:34:50 +0000 (UTC) Cc: jearl@notengoamigos.org, ian.clatworthy@canonical.com, emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 20 14:34:43 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 1NBTdK-0008O0-HR for ged-emacs-devel@m.gmane.org; Fri, 20 Nov 2009 14:34:42 +0100 Original-Received: from localhost ([127.0.0.1]:59128 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBTdJ-0003ya-Np for ged-emacs-devel@m.gmane.org; Fri, 20 Nov 2009 08:34:41 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBTdD-0003ws-N4 for emacs-devel@gnu.org; Fri, 20 Nov 2009 08:34:35 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBTd8-0003rZ-FZ for emacs-devel@gnu.org; Fri, 20 Nov 2009 08:34:34 -0500 Original-Received: from [199.232.76.173] (port=56778 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBTd8-0003rU-Bk for emacs-devel@gnu.org; Fri, 20 Nov 2009 08:34:30 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:40532) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NBTd7-00065G-OH for emacs-devel@gnu.org; Fri, 20 Nov 2009 08:34:30 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0KTE00F00TJ6QK00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Fri, 20 Nov 2009 15:34:28 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.70.37.193]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KTE00ESWTPFSF30@a-mtaout22.012.net.il>; Fri, 20 Nov 2009 15:34:28 +0200 (IST) In-reply-to: <87my2jw05z.fsf@red-bean.com> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) 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:117348 Archived-At: > From: Karl Fogel > Date: Thu, 19 Nov 2009 00:31:20 -0500 > Cc: Andreas Schwab , > Jason Earl , > Ian Clatworthy , emacs-devel@gnu.org > > Alan Mackenzie writes: > > Please wait until the 23.2 pretest is out. It's only a few more days > > (?end of November?). > > Sure -- makes sense to me. Also, would it be possible to publish a short ``howto'' cookbook for those who are not familiar enough with bzr? A DVCS has more different workflows than CVS and its ilk, so it would be good if active developers could know up front how to set up and how to use the workflow that best fits their needs, without having to read lots of unnecessary documentation and finding that out by trial and error. At least the following important workflows come to mind: . Development on the trunk -- sync with the main repository, make changes, submit them back to the repository. . Development on a release branch -- same as above, except that changes go to a branch. . Development on a public branch -- this would include more merges from and to the trunk, and otherwise is like the second bullet above. . Development on a private branch. (Maybe there are more -- I have no real experience with a DVCS, so I don't know.) For each one of these, it would be enough to point to the relevant sections of the existing bzr docs, no need to rewrite them, unless some of the issues are mal-documented. In addition, some guidelines for selecting the right version of bzr that should be installed, and if there are more than one that's suitable, a short list of advantages and disadvantages of each of them. Finally, some guidance for users on Windows, if there are any issues that need special attention (EOL format comes to mind, as well as binary files, but maybe there's more). TIA