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: Please don't use revision numbers on commit messages (and elsewhere). Date: Fri, 01 Apr 2011 11:18:01 +0300 Message-ID: <83wrjepepy.fsf@gnu.org> References: <877hbfvwyo.fsf@wanadoo.es> <87tyeivni1.fsf@wanadoo.es> <87k4fevkc1.fsf@wanadoo.es> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: dough.gmane.org 1301645956 14099 80.91.229.12 (1 Apr 2011 08:19:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 1 Apr 2011 08:19:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 01 10:19:11 2011 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 1Q5ZZW-0004UM-GB for ged-emacs-devel@m.gmane.org; Fri, 01 Apr 2011 10:19:11 +0200 Original-Received: from localhost ([127.0.0.1]:36513 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q5ZZU-0006xC-L9 for ged-emacs-devel@m.gmane.org; Fri, 01 Apr 2011 04:19:08 -0400 Original-Received: from [140.186.70.92] (port=50699 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q5ZZI-0006wa-RK for emacs-devel@gnu.org; Fri, 01 Apr 2011 04:19:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q5ZZE-00006C-5V for emacs-devel@gnu.org; Fri, 01 Apr 2011 04:18:53 -0400 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:48508) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q5ZZD-00005Z-V8 for emacs-devel@gnu.org; Fri, 01 Apr 2011 04:18:52 -0400 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0LIY00400S4WI100@a-mtaout23.012.net.il> for emacs-devel@gnu.org; Fri, 01 Apr 2011 11:18:00 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([77.126.47.180]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LIY004DPSDYFI70@a-mtaout23.012.net.il>; Fri, 01 Apr 2011 11:18:00 +0300 (IDT) In-reply-to: <87k4fevkc1.fsf@wanadoo.es> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.175 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:137975 Archived-At: > From: =C3=93scar Fuentes > Date: Fri, 01 Apr 2011 03:20:14 +0200 >=20 > Anyone can setup a public repo anytime, anywhere. Let's think of a > long-lived feature branch of the type of lexbind or bidi The bidi branch was never alive for a long time. If anything, it was _dead_ for a long time. Once serious work on bidi support was resumed, and it was in a shape that could be used without crashing every several seconds, it was merged with the trunk. In general, the current experience with branches seems to be that no one but their developer(s), usually a single individual, uses them, until very close to a merge. The only exception is the release branch, where the maintainers take care of these references. So it looks like you are asking everyone and their dog to pay dearly _now_ for a mostly theoretical problem, that could potentially become a real problem in some vague future. Good luck expecting that people will abide by your request! > On a distributed project, you don't know how many active branches e= xist > out there. Emacs is not currently a distributed project, and I see no signs that it is going to become one. > Let me expand with an example based on my past* experience. I have = a > number of heterogeneous machines (different OS, varying network > connectivity, etc) and on all of them I have Emacs running (of > course!). I've my private branch with some customizations, which is= what > I use for building and installing Emacs on all those machines. Keep= ing > the private branch mirrored among all of them means work. Keeping > mirrors for `trunk', emacs-23 and what-not is too much of a burden = (last > time I checked there was no simple & reliable method for synchroniz= ing > sets of branches across multiple platforms.) In theory, having just= my > private branch and merging trunk into it from time to time would be > enough. But then those commits messages referencing other revisions= by > their numbers doesn't fit, as trunk's revision #110000 has another > number on my private branch. It is very easy to see that revision, even if it is on the other branch, assuming that the referenced branch is in your repo, with the "revno:NNN:/path/to/branch" revision identifier. > Do you prefer to wait until the problem has manifested itself on al= l its > crudeness? :-) That's one way of putting it. Another one would be "don't try to solve problems that don't exist."