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: bzr repository ready? Date: Sun, 22 Nov 2009 06:25:19 +0200 Message-ID: <83tywnnq34.fsf@gnu.org> References: <87639fr3w7.fsf@red-bean.com> <87vdhfpil2.fsf@red-bean.com> <87einvxy9c.fsf@red-bean.com> <20091118230952.GB908@muc.de> <87my2jw05z.fsf@red-bean.com> <83skc9pbf7.fsf@gnu.org> <87iqd5vw5n.fsf@red-bean.com> <877htl53tc.fsf@telefonica.net> <87ws1ku7zd.fsf@red-bean.com> <87hbso4s13.fsf@telefonica.net> <83aaygoy90.fsf@gnu.org> <87vdh36d48.fsf@telefonica.net> <831vjrptha.fsf@gnu.org> <87einr63b6.fsf@telefonica.net> <83y6lzo9e7.fsf@gnu.org> <871vjr750o.fsf@uwakimon.sk.tsukuba.ac.jp> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1258863942 11612 80.91.229.12 (22 Nov 2009 04:25:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 22 Nov 2009 04:25:42 +0000 (UTC) Cc: ofv@wanadoo.es, emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 22 05:25:35 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 1NC411-0004BJ-2J for ged-emacs-devel@m.gmane.org; Sun, 22 Nov 2009 05:25:35 +0100 Original-Received: from localhost ([127.0.0.1]:35675 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NC410-00051Q-BT for ged-emacs-devel@m.gmane.org; Sat, 21 Nov 2009 23:25:34 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NC40u-00051A-Cn for emacs-devel@gnu.org; Sat, 21 Nov 2009 23:25:28 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NC40o-0004xQ-Uj for emacs-devel@gnu.org; Sat, 21 Nov 2009 23:25:27 -0500 Original-Received: from [199.232.76.173] (port=45782 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NC40o-0004xK-Rx for emacs-devel@gnu.org; Sat, 21 Nov 2009 23:25:22 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:58429) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NC40o-0007cE-Dr for emacs-devel@gnu.org; Sat, 21 Nov 2009 23:25:22 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0KTH00800TDYXT00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Sun, 22 Nov 2009 06:25:21 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.70.37.193]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KTH002WUTM5OVK0@a-mtaout22.012.net.il>; Sun, 22 Nov 2009 06:25:21 +0200 (IST) In-reply-to: <871vjr750o.fsf@uwakimon.sk.tsukuba.ac.jp> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) 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:117481 Archived-At: > From: "Stephen J. Turnbull" > Cc: =?iso-8859-1?Q?=D3scar?= Fuentes , > emacs-devel@gnu.org > Date: Sun, 22 Nov 2009 09:54:47 +0900 > > If you do this in git (and in git, I do!), it's painless, because you > have only one workspace for all the small changes. The branches are > "colocated" in the same repository/workspace; they share a working > tree. That means that a rebuild is a simple `make', and it's > incremental. But Bazaar branches *cannot* at present be colocated; > they *cannot* share a working tree. That means that if you do a > "bzr branch" for a one-line change, you have to do a "make bootstrap" > to test. EEEEEEeeeeeewwwwww. For someone who comes from CVS (and centralized VCS in general), this aspect is a no-brainer. > You are. *You* apparently don't miss having the VCS record your > history as you go along, and that's OK. As I wrote elsewhere, I do have history. > For your use case, where you don't care about history, you're right; > it's hard to beat CVS by very much. Until a year from now, when > Yidong comes to you and says, "what were you thinking when you wrote > this code?!" and you are forced to say "I don't know" I have full records of my design decisions and the history of changes. So I will be able to answer such questions easily enough. Not everything in this world needs to be recorded in a VCS to be readily available. Especially if only one individual is working on a project. > and you make the > "obvious" fix and 6 months after *that* somebody inserts an Arabic > obscenity into a letter to their mother because it's "I love you" > spelled backwards.... A VCS is no panacea from bugs. > Of course there are other ways to accomplish this kind of history- > keeping, such as comments in the code and entries in the ChangeLog > proper (lord, do I hate merging changelogs!) Again, if that works for > you, OK. But I and many others find it useful to have the VCS manage > that task, specifically because unlike a ChangeLog, it provides the > exact patch that goes with the changelog. I'm fine with that, I just said that I don't see how a VCS can "shine" in my case.