From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: `about-emacs' - what about the revno? Date: Wed, 01 Sep 2010 08:20:40 +0200 Message-ID: References: <83occmlogo.fsf@gnu.org> <834oeckqv3.fsf@gnu.org> <83wrr8j8g5.fsf@gnu.org> <87hbia8s08.fsf@telefonica.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1283322102 3948 80.91.229.12 (1 Sep 2010 06:21:42 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 1 Sep 2010 06:21:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 01 08:21:40 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 1OqghW-0002Qe-KG for ged-emacs-devel@m.gmane.org; Wed, 01 Sep 2010 08:21:38 +0200 Original-Received: from localhost ([127.0.0.1]:57919 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OqghV-0007go-UR for ged-emacs-devel@m.gmane.org; Wed, 01 Sep 2010 02:21:37 -0400 Original-Received: from [140.186.70.92] (port=38451 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oqggk-0007Ow-R9 for emacs-devel@gnu.org; Wed, 01 Sep 2010 02:20:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oqggd-0000Ut-Fs for emacs-devel@gnu.org; Wed, 01 Sep 2010 02:20:50 -0400 Original-Received: from impaqm4.telefonica.net ([213.4.138.4]:18857) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oqggd-0000Ua-96 for emacs-devel@gnu.org; Wed, 01 Sep 2010 02:20:43 -0400 Original-Received: from IMPmailhost2.adm.correo ([10.20.102.39]) by IMPaqm4.telefonica.net with bizsmtp id 1J8J1f0070r0BT63QJLhSu; Wed, 01 Sep 2010 08:20:41 +0200 Original-Received: from ceviche.home ([83.40.7.141]) by IMPmailhost2.adm.correo with BIZ IMP id 1JLg1f00432ZxvX1iJLhBP; Wed, 01 Sep 2010 08:20:41 +0200 X-Brightmail-Tracker: AAAAAA== X-TE-authinfo: authemail="monnier$movistar.es" |auth_email="monnier@movistar.es" X-TE-AcuTerraCos: auth_cuTerraCos="cosuitnetc01" Original-Received: by ceviche.home (Postfix, from userid 20848) id 7ADF2660DF; Wed, 1 Sep 2010 08:20:40 +0200 (CEST) In-Reply-To: <87hbia8s08.fsf@telefonica.net> (=?iso-8859-1?Q?=22=D3scar?= Fuentes"'s message of "Tue, 31 Aug 2010 22:08:23 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. 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:129532 Archived-At: >>>> PS: As mentioned earlier, it requires internet access. >>> I thought bzr is a dVCS? >> Yes, but we want to relate someone's code to the one in our >> repository. > The question here is: are you interested on bug reports coming from > builds that contains unknown modifications? Not terribly, but we have handled some such reports in the past (Debian and a few others come to mind). And I think we want to encourage people to develop local patches in their local branches (with the hope they'll contribute them eventually), as well as encourage people to report bugs, so yes, I think we are interested. We usually accept the report, tho we also often ask people to try and reproduce the bug on a vanilla build. > (I guess that at some point into the future bug reports for sanctioned > feature branches will be accepted too. Actually, that's already the case since we have both the trunk and the emacs-23 branch (not exactly "feature branches", but the problem is the same). > Then, the "common ancestor with trunk" approach will need an overhaul. It already does. We want "nick+revno+changes" where "nick" is the name of one of the branches in our repository and "changes" is some representation of the changes relative to "nick+revno". Can be just a boolean indicating whether there are changes, or it could be something else like the "bzr diff|wc" I suggested. Stefan