From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: New sync'd branch Date: Fri, 28 Aug 2009 21:33:57 +0200 Organization: Organization?!? Message-ID: <87eiqv7mxm.fsf@lola.goethe.zz> 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> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1251493351 19686 80.91.229.12 (28 Aug 2009 21:02:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 28 Aug 2009 21:02:31 +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:02:24 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 1Mh8aW-0000LY-1d for ged-emacs-devel@m.gmane.org; Fri, 28 Aug 2009 23:02:24 +0200 Original-Received: from localhost ([127.0.0.1]:58141 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh8aV-0003uH-I5 for ged-emacs-devel@m.gmane.org; Fri, 28 Aug 2009 17:02:23 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mh7DU-0002Wx-SH for emacs-devel@gnu.org; Fri, 28 Aug 2009 15:34:32 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh7DP-0002Wc-Sj for emacs-devel@gnu.org; Fri, 28 Aug 2009 15:34:32 -0400 Original-Received: from [199.232.76.173] (port=58615 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh7DP-0002WZ-Lv for emacs-devel@gnu.org; Fri, 28 Aug 2009 15:34:27 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:37252) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mh7DN-0003zi-Rk for emacs-devel@gnu.org; Fri, 28 Aug 2009 15:34:27 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1Mh7DI-0001gF-UX for emacs-devel@gnu.org; Fri, 28 Aug 2009 21:34:20 +0200 Original-Received: from p5b2c24c5.dip.t-dialin.net ([91.44.36.197]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Aug 2009 21:34:20 +0200 Original-Received: from dak by p5b2c24c5.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Aug 2009 21:34:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 79 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p5b2c24c5.dip.t-dialin.net X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:qCINE6mP48/8JDF3OFFZANLmRB0= 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:114785 Archived-At: Óscar Fuentes writes: > David Kastrup writes: > >> Óscar Fuentes writes: >> >>> Finally, git's UI is horrid: complex, barroque, with plenty of >>> opportunities for shooting yourself on the feet. >> >> But there is the reflog. After shooting yourself in the foot, you >> always have the option of going back to before the shot. >> >> 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. >> 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. >>> Some day people will recognize this and will see today's massive >>> leaning towards git as a mistake originated on juvenile reverence >>> towards its original author and on simplistic metrics like raw >>> speed, putting aside a critical and objetive assessment of its >>> merits compared against the alternatives. >> >> You underestimate git. And you underestimate "people". Torvalds >> usually does several hundreds of merges a day. > > 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". >> And that's not just because of "raw speed", but also because of >> high-quality merging strategies. > > 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. >> 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. > git's problems (mostly UI and poor support for non-POSIX environments) > will not be solved anytime soon. "Stay with our stuff, it is slated to get better. The stuff that works better is bad for you" has quite rarely made good on its promises in my experience. -- David Kastrup