From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Please don't use revision numbers on commit messages (and elsewhere). Date: Fri, 01 Apr 2011 17:35:58 +0200 Message-ID: <874o6iugpt.fsf@wanadoo.es> References: <877hbfvwyo.fsf@wanadoo.es> <87tyeivni1.fsf@wanadoo.es> <87k4fevkc1.fsf@wanadoo.es> <83wrjepepy.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1301673242 16006 80.91.229.12 (1 Apr 2011 15:54:02 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 1 Apr 2011 15:54:02 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 01 17:53:58 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 1Q5gco-00072B-7F for ged-emacs-devel@m.gmane.org; Fri, 01 Apr 2011 17:53:58 +0200 Original-Received: from localhost ([127.0.0.1]:49400 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q5gYn-0006tC-Cu for ged-emacs-devel@m.gmane.org; Fri, 01 Apr 2011 11:46:53 -0400 Original-Received: from [140.186.70.92] (port=56602 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q5gOb-0006zt-30 for emacs-devel@gnu.org; Fri, 01 Apr 2011 11:36:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q5gOT-00051i-KS for emacs-devel@gnu.org; Fri, 01 Apr 2011 11:36:15 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:34419) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q5gOT-00051M-9O for emacs-devel@gnu.org; Fri, 01 Apr 2011 11:36:13 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Q5gOR-0007kp-8A for emacs-devel@gnu.org; Fri, 01 Apr 2011 17:36:11 +0200 Original-Received: from 131.red-83-59-5.dynamicip.rima-tde.net ([83.59.5.131]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Apr 2011 17:36:11 +0200 Original-Received: from ofv by 131.red-83-59-5.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Apr 2011 17:36:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 56 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 131.red-83-59-5.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:wPjyIR25a7pGNY/cVT2cxD+RivQ= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:138005 Archived-At: Eli Zaretskii writes: >> 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. bidi was mentioned as an example of a task suitable for a long lived feature branch (and for working on a team, or at least publish the branch and accept occasional contributions.) I was not implying that bidi was actually managed that way. [snip] > 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! It is not mostly theoretical. It would be affecting me if I were using bzr (and then it would be another reason for switching to git.) >> On a distributed project, you don't know how many active branches exist >> out there. > > Emacs is not currently a distributed project, and I see no signs that > it is going to become one. No, you see no signs because private branches live on private machines, which is precisely one of the specific characteristics of a dVCS. I have two branches where I do development since a year ago. I'm sure you wasn't aware of their existence until now :-) >> 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. Keeping >> 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 synchronizing >> 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. Precisely, what I described above was a setup where having the "other branch" (say better "the other brancheS") is a burden. So I don't have them. [snip]