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: Sun, 22 Nov 2009 17:30:18 -0600 Message-ID: <87zl6e9lyt.fsf@red-bean.com> 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 1258932645 21264 80.91.229.12 (22 Nov 2009 23:30:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 22 Nov 2009 23:30:45 +0000 (UTC) Cc: ofv@wanadoo.es, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 23 00:30:38 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 1NCLt3-0004ZM-Mk for ged-emacs-devel@m.gmane.org; Mon, 23 Nov 2009 00:30:34 +0100 Original-Received: from localhost ([127.0.0.1]:33279 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCLt3-0006El-0F for ged-emacs-devel@m.gmane.org; Sun, 22 Nov 2009 18:30:33 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCLsy-0006EU-2O for emacs-devel@gnu.org; Sun, 22 Nov 2009 18:30:28 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCLst-0006Da-Rm for emacs-devel@gnu.org; Sun, 22 Nov 2009 18:30:27 -0500 Original-Received: from [199.232.76.173] (port=47444 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCLst-0006DX-Kc for emacs-devel@gnu.org; Sun, 22 Nov 2009 18:30:23 -0500 Original-Received: from sanpietro.red-bean.com ([66.146.206.141]:59061) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NCLsq-0000sm-D1; Sun, 22 Nov 2009 18:30:20 -0500 Original-Received: from localhost ([127.0.0.1]:35627 helo=kfogel-work ident=kfogel) by sanpietro.red-bean.com with esmtp (Exim 4.69) (envelope-from ) id 1NCLsp-0007NW-6f; Sun, 22 Nov 2009 17:30:19 -0600 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:117518 Archived-At: Eli Zaretskii writes: >> http://www.emacswiki.org/emacs/BzrForEmacsDevs#RegularContributors > > What I'm missing from that description is how do I get my branch > available to others. I'm guessing that there's a possibility to have > the branch in the master repository, and there's another possibility > to have my local branch published from my machine directly. But the > wiki currently describes neither of these two (apologies if it does, > and I missed that). Sorry, I only answered half of your question in my previous mail, the half about how to publish changes to the master repository. For publishing your changes on your own, without involving the master repository, see the Bazaar Users guide. I know that sounds like "talk to the hand", but IMHO we need to avoid duplicating all the existing Bazaar documentation in our Emacs-specific doc. Our document should tell Emacs developers specifically what they need that isn't covered or isn't easy to find in the existing docs. So for example, Emacs devs need a recommendation for exactly how to set up a shared repository / branches locally, in a way that will work well with typical Emacs development. We should provide that. But as for publishing branches independently -- there are many ways to do that, they're all pretty easy, and none of them are really specific to Emacs development. The answers to such questions should be found in the generic Bazaar documentation, and where that documentation is insufficient, it should be improved in place. (If I knew one good answer to your question, I'd say it here, of course, but there are many ways to publish Bazaar branches, starting with "just make your shared repository all accessible via http://"... beyond that, it just depends what kind of access control you want and other factors. I can't give a better answer than the Bazaar docs would provide.) -Karl