From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?windows-1252?Q?=D3scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: New sync'd branch Date: Fri, 28 Aug 2009 23:41:08 +0200 Message-ID: <87prafliq3.fsf@telefonica.net> References: <878wh9qaku.fsf@sphinx.net.ru> <83praic5r5.fsf@gnu.org> <83d46gcnsb.fsf@gnu.org> <87ocq0l2hw.fsf@iki.fi> <83ab1kcmi5.fsf@gnu.org> <877hwom4og.fsf@telefonica.net> <878wh47z7z.fsf@lola.goethe.zz> <87y6p3luq3.fsf@telefonica.net> <87eiqv7mxm.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1251496358 28271 80.91.229.12 (28 Aug 2009 21:52:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 28 Aug 2009 21:52:38 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 28 23:52:31 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 1Mh9Mu-0006Fi-SM for ged-emacs-devel@m.gmane.org; Fri, 28 Aug 2009 23:52:25 +0200 Original-Received: from localhost ([127.0.0.1]:44906 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh9Mu-0006Bj-9V for ged-emacs-devel@m.gmane.org; Fri, 28 Aug 2009 17:52:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh9CX-00008o-67 for emacs-devel@gnu.org; Fri, 28 Aug 2009 17:41:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh9CR-0008ON-BB for emacs-devel@gnu.org; Fri, 28 Aug 2009 17:41:39 -0400 Original-Received: from [199.232.76.173] (port=33440 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh9CR-0008OD-7l for emacs-devel@gnu.org; Fri, 28 Aug 2009 17:41:35 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:51275) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mh9CQ-0005Ey-CW for emacs-devel@gnu.org; Fri, 28 Aug 2009 17:41:34 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1Mh9CM-0002vo-Ra for emacs-devel@gnu.org; Fri, 28 Aug 2009 23:41:30 +0200 Original-Received: from 96.red-83-52-52.dynamicip.rima-tde.net ([83.52.52.96]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Aug 2009 23:41:30 +0200 Original-Received: from ofv by 96.red-83-52-52.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Aug 2009 23:41:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 76 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 96.red-83-52-52.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:cLMIPKAFwbovL4ZGgsF2Kvol/u4= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) 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:114792 Archived-At: David Kastrup writes: >>> Yes, it is reasonably easy to blow up some operation terribly if you >>> don't know what you are doing. Because git has lots of power. But >>> you always can tell it: "Ok, this was a complete messup. Give me >>> back what I had 20 minutes ago". >> >> I'll really apreciate a tool that does not make me waste those 20 >> minutes. > > It saves you hours elsewhere. Compared against the other DVCS's? Not on my experience. git's speed advantage is not *that* large. >>> It is very hard to actually do something which can't be undone. You >>> have to really try. >> >> And this is different from other VCSs how? > > No impact on a central repository even when you tried some complex merge > and got it wrong. Nobody gets to see your damaged foot. You just > messed up your personal sandbox temporarily. I insist: and this is different from other VCS how? Does git block you from sending your changes upstream when you messed up your personal repo? If you screw up your personal branch, bzr notices it and maliciously sends the changes upstream without you asking for it? >> The typical Emacs developer is not like Torvads. Emacs has a >> development style that is very far from Linux's. Every example about >> how well git works specifically for Torvalds is moot. > > That sounds like "nobody will ever need a car, because people ride > horses quite differently than they would ride a car". Often, a car is the worst option as a vehicle. >> git's mergin strategies are possibly superior to bzr, but do we (Emacs >> and most other Free projects) really need them? I think not. > > Do we really need cars? I think not. > > I've been the designated merger for diverging feature branches at the > last company I worked with. Because I was used to working with git. > The VCS at the company was Subversion. Subversion is quite better with > regard to merging than CVS ever was. Still I was able to do this stuff > quite more thoroughly and faster with git. And with "faster" I mean the > investment of human time, not computing time. I was talking about bzr vs git for merging. hg vs git fits too. Now you talk about svn, which merging support is basic, to say it softly. If you keep changing your counterexample for making git look infinitely better at every point, this discussion has no value. >>> Moving Emacs towards Bazaar was a real stress test for >>> Bazaar, and still is. >> >> This will be fixed over time. > > That's the sort of sentence in software development environments that > sets off all my alarms. There is a clear concern and involvement among bzr developers about improving performance and almost everything else. I can't see much concern about UI and multi-platform support when I read git's mailing list, though. [snip] -- Óscar Fuentes Desarrollo de Software