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: Fri, 20 Nov 2009 14:22:28 -0500 Message-ID: <87iqd5vw5n.fsf@red-bean.com> 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> 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 1258744992 16547 80.91.229.12 (20 Nov 2009 19:23:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 20 Nov 2009 19:23:12 +0000 (UTC) Cc: jearl@notengoamigos.org, ian.clatworthy@canonical.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 20 20:23:04 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 1NBZ4Q-0004pj-My for ged-emacs-devel@m.gmane.org; Fri, 20 Nov 2009 20:23:02 +0100 Original-Received: from localhost ([127.0.0.1]:55713 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBZ4Q-00030w-5U for ged-emacs-devel@m.gmane.org; Fri, 20 Nov 2009 14:23:02 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBZ43-0002gR-Mo for emacs-devel@gnu.org; Fri, 20 Nov 2009 14:22:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBZ3z-0002ch-R0 for emacs-devel@gnu.org; Fri, 20 Nov 2009 14:22:39 -0500 Original-Received: from [199.232.76.173] (port=34434 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBZ3z-0002cM-LX for emacs-devel@gnu.org; Fri, 20 Nov 2009 14:22:35 -0500 Original-Received: from sanpietro.red-bean.com ([66.146.206.141]:50401) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NBZ3w-0000SO-B3; Fri, 20 Nov 2009 14:22:32 -0500 Original-Received: from localhost ([127.0.0.1]:44438 helo=kfogel-work ident=kfogel) by sanpietro.red-bean.com with esmtp (Exim 4.69) (envelope-from ) id 1NBZ3t-0000HB-Nn; Fri, 20 Nov 2009 13:22:30 -0600 In-Reply-To: <83skc9pbf7.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Nov 2009 15:34:36 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (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:117373 Archived-At: Eli Zaretskii writes: > 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.) My sympathies -- I came to bzr from the centralized-vc world too. It's actually not that hard though. You just have to separate the concept of "checkpoint my work" from the concept of "publish my work". In centralized vc, these are unified in the "commit" command. In Bazaar, "commit" means "checkpoint" and "push" means "publish" (roughly speaking). I've already written http://www.emacswiki.org/emacs/BzrForEmacsDevs. My instinct is to start with that, and then answer questions here as as people have them, rather than write lots more text only to discover that it doesn't answer the questions that actually come up. > 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. The above has a link to the Bazaar Users Guide, and other things. > 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. A version recommendation is already at the above link. > 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). That I can't help with (Windows-free since 1992), but there are plenty of Bazaar Windows users and an active user community in general. See http://bazaar-vcs.org/ for details. -Karl