From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: New sync'd branch
Date: Fri, 28 Aug 2009 21:33:57 +0200 [thread overview]
Message-ID: <87eiqv7mxm.fsf@lola.goethe.zz> (raw)
In-Reply-To: 87y6p3luq3.fsf@telefonica.net
Óscar Fuentes <ofv@wanadoo.es> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> Óscar Fuentes <ofv@wanadoo.es> 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
next prev parent reply other threads:[~2009-08-28 19:33 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 22:21 New sync'd branch Stefan Monnier
2009-08-23 22:35 ` joakim
2009-08-24 13:58 ` Leo
2009-08-24 19:24 ` Dmitry Dzhus
2009-08-25 17:44 ` Stefan Monnier
2009-08-26 8:31 ` Miles Bader
2009-08-26 19:04 ` Stefan Monnier
2009-08-27 3:09 ` Eli Zaretskii
2009-08-27 4:47 ` Miles Bader
2009-08-27 5:38 ` Teemu Likonen
2009-08-28 8:34 ` Eli Zaretskii
2009-08-27 6:33 ` Ken Raeburn
2009-08-27 7:08 ` Teemu Likonen
2009-08-27 7:14 ` Christian Faulhammer
2009-08-27 8:55 ` Ken Raeburn
2009-08-27 9:07 ` Miles Bader
2009-08-27 10:11 ` Stephen J. Turnbull
2009-08-28 9:18 ` Eli Zaretskii
2009-08-27 9:47 ` joakim
2009-08-28 9:04 ` Eli Zaretskii
2009-08-28 9:12 ` Miles Bader
2009-08-28 9:19 ` Teemu Likonen
2009-08-28 9:32 ` Eli Zaretskii
2009-08-28 13:03 ` David Kastrup
2009-08-28 13:46 ` Óscar Fuentes
2009-08-28 14:55 ` Juanma Barranquero
2009-08-28 17:11 ` Óscar Fuentes
2009-08-28 17:49 ` Juanma Barranquero
2009-08-28 18:00 ` David Reitter
2009-08-29 3:56 ` Stephen J. Turnbull
2009-08-29 20:20 ` Richard Stallman
2009-08-28 15:08 ` David Kastrup
2009-08-28 17:21 ` Óscar Fuentes
2009-08-28 19:33 ` David Kastrup [this message]
2009-08-28 21:41 ` Óscar Fuentes
2009-08-28 22:20 ` Miles Bader
2009-08-28 22:55 ` Óscar Fuentes
2009-08-29 0:17 ` Miles Bader
2009-08-29 9:08 ` David Kastrup
2009-08-29 15:25 ` Stefan Monnier
2009-08-29 0:46 ` Stefan Monnier
2009-08-28 22:00 ` Miles Bader
2009-08-28 14:01 ` Juanma Barranquero
2009-08-28 14:08 ` Eli Zaretskii
2009-08-28 14:13 ` Juanma Barranquero
2009-08-28 14:33 ` Eli Zaretskii
2009-08-28 14:44 ` Juanma Barranquero
2009-08-28 9:38 ` joakim
2009-08-28 9:48 ` Eli Zaretskii
2009-08-28 10:02 ` Eli Zaretskii
2009-08-28 11:18 ` David Kastrup
2009-08-28 15:59 ` David Reitter
2009-08-27 21:27 ` Stefan Monnier
2009-08-28 8:28 ` Eli Zaretskii
2009-08-27 21:52 ` Glenn Morris
2009-08-27 22:17 ` Chong Yidong
-- strict thread matches above, loose matches on Subject: below --
2009-08-24 22:25 Nick Roberts
2009-08-25 9:29 ` joakim
2009-08-25 14:06 ` Chong Yidong
2009-08-25 21:02 ` Nick Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eiqv7mxm.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.