emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: base


From: Stephen J. Turnbull
Subject: Re: base
Date: Wed, 25 Aug 2010 02:35:24 +0900

Juanma Barranquero writes:
 > On Tue, Aug 24, 2010 at 14:32, Stephen J. Turnbull
 > <address@hidden> wrote:
 > 
 > > (except maybe Eli because of the Windows issues)

 > The "Windows issues" are quite real.

Granted.  However, they're real for *all* DVCSes.

 > So Bzr, with all its problems, at least has some compromise of
 > supporting Windows users, while on git it seems like we're barely
 > tolerated :-)

I can't speak to the git side; I've never *ever* had enough trouble
with git to need to get in touch with their MLs.  ISTM that while the
Bazaar devs pay lip service to Windows issues, they don't go much
beyond that (and some issues like SSH configuration on Windows just
don't ever seem to go away).

 > > but the UI badmouthing kept the discussion going
 > > long enough for other candidates to get serious consideration.

 > My English isn't good enoug to know whether "badmouthing" implies
 > falsehood or bad intention.

It implies both.

 > That the UI is bad is IMHO entirely true.

You are of course welcome to your opinion, and there's no need to be
humble about it.

I find your opinion hard to understand, however, because in basic,
everyday usage git is *simpler* than bzr.  You have essentially the
same number of commands, they do mostly the same things: init, clone
(missing in bzr), add, rm, mv (optional in git), commit, status, diff,
log, pull, push, branch, checkout (optional with different semantics
in bzr), reset (no single equivalent in bzr), merge: total 15
commands.  Except that that's not enough to use bzr efficiently; bzr
needs at least init-repo, and for many workflows update and switch
(and checkout becomes required).  That need is not obvious.

It's true that specification of revisions in git is unfamiliar.  But
both hg and bzr have been forced to add git notation by popular
demand.  And I think it would be very odd for someone who's familiar
with operators like "nthcdr" (which is "~" in git revision notation)
to complain about it.  It's rare to need any other notation (except in
quite specialized situations).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]