From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bojan Nikolic Newsgroups: gmane.emacs.devel Subject: Re: bzr send workflow Date: Sun, 22 Aug 2010 15:40:03 +0100 Message-ID: <87eidqyam4.fsf@bnikolic.co.uk> References: <87occvzosg.fsf@bnikolic.co.uk> <87lj7z6pyn.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1282489247 5563 80.91.229.12 (22 Aug 2010 15:00:47 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 22 Aug 2010 15:00:47 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 22 17:00:45 2010 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.69) (envelope-from ) id 1OnC2K-0005jf-Bo for ged-emacs-devel@m.gmane.org; Sun, 22 Aug 2010 17:00:40 +0200 Original-Received: from localhost ([127.0.0.1]:59719 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OnC2J-00025t-Sl for ged-emacs-devel@m.gmane.org; Sun, 22 Aug 2010 11:00:39 -0400 Original-Received: from [140.186.70.92] (port=33469 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OnBjj-0006ek-4n for emacs-devel@gnu.org; Sun, 22 Aug 2010 10:41:31 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OnBiT-0002d8-NB for emacs-devel@gnu.org; Sun, 22 Aug 2010 10:40:20 -0400 Original-Received: from out1.smtp.messagingengine.com ([66.111.4.25]:55036) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OnBiT-0002ca-GE for emacs-devel@gnu.org; Sun, 22 Aug 2010 10:40:09 -0400 Original-Received: from compute3.internal (compute3.internal [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3F5FF1FE; Sun, 22 Aug 2010 10:40:08 -0400 (EDT) Original-Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Sun, 22 Aug 2010 10:40:08 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=from:to:cc:subject:references:date:in-reply-to:message-id:mime-version:content-type; s=smtpout; bh=gYkt0pGikaQ3aw3AbYrcs/AI/sM=; b=MFMQB7gfCBlQC8Pjc3XG9ix+ZwZ9Gf3HUJ3WOWUG5a+zRLcK6/2ytj5enXZVgUjbKqXrrFn0r7qAemQWlMqwNdhc1GgUcHJPRG+JJZBfFw5I2lBEsXz1GQFULnFGzP/vxlqhaiF0q68BS+eEy6CCTJy2d6wjVolh21uLifbbI88= X-Sasl-enc: bEcbBNwfLdYNGfvzvCoF31QUI+Fw4M/rZb3o7Guk97NG 1282488007 Original-Received: from bnikolic-laptop (nat-01.alma.cl [200.2.0.129]) by mail.messagingengine.com (Postfix) with ESMTPSA id 8080E5E9795; Sun, 22 Aug 2010 10:40:07 -0400 (EDT) In-Reply-To: <87lj7z6pyn.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Sun, 22 Aug 2010 16:56:00 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Mailman-Approved-At: Sun, 22 Aug 2010 11:00:35 -0400 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:129042 Archived-At: "Stephen J. Turnbull" writes: > Bojan Nikolic writes: > > > As already much discussed, the problems people are experiencing are > > basically due to many people trying to write (in some way) to the > > same sftp://bzr.sv.gnu.org/srv/bzr/emacs/trunk/ location via the > > dumb sftp protocol. > > > > There are many ways around this, but one I did not see mentioned > > (maybe I missed it) is using the bzr send command to send merge > > "bundles" via email. This is the way bzr development itself worked > > while I followed it, and I've used it on some of my own projects > > too. I was always very impressed how well it worked. > > I don't think this helps much. The underlying problem for Emacs (and > other bzr-based projects on Savannah) is that Savannah doesn't want to > allow bzr+ssh until the Savannah admins understand the security > implications. The Bazaar development workflow involves at least one > separate server application not yet available on Savannah (the pqm > Patch Queue Manager), and I can't imagine that installing that would > be any easier than upgrading already installed software to use a smart > server over ssh. My idea was that in the first instance the bundles would be merged by (a select group of) people. These people would either have a fast connection to the bzr.sv.gnu.org, or even better, a login to the machine hosting this branch, in which case the merges could be done without any network traffic. It is a bit of an overhead but it takes only a few seconds to do a merge of bundle from Gnus. This has the additional benefit that most changes would have four eyes on them before being committed to the trunk. To reiterate the main benefit though: accepting "bzr send" bundles means that people on even the slowest connections can contribute easily and efficiently. I've used these satisfactorily over slow GPRS connections. Best, Bojan -- Bojan Nikolic || http://www.bnikolic.co.uk