From: Yuri Khan <yuri.v.khan@gmail.com>
To: Neal Becker <ndbecker2@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: preferring mercurial
Date: Thu, 9 Jan 2014 22:42:17 +0700 [thread overview]
Message-ID: <CAP_d_8W1rVOsYzQDbMxOX17540-DvTv-kgJonDLQ1-ug=q-ASg@mail.gmail.com> (raw)
In-Reply-To: <lam51v$gh6$1@ger.gmane.org>
On Thu, Jan 9, 2014 at 7:35 PM, Neal Becker <ndbecker2@gmail.com> wrote:
> I don't understand the git momentum. I've use hg heavily, and am generally
> happy with it.
I use git heavily, and am happy with it. Except that I wish gitk and
git gui were more keyboard-friendly.
> Every time I have to use git, I have a terrible time. I find it vastly more
> complicated than hg. The docs (in the form of man pages) I find never answer my
> questions. Each one seems to cover 100 different topics, variations and corner
> cases. Trying to read this requires a vast new vocabulary or arcane terms.
If you want answers, read “Pro Git”, not manuals. Manuals are for when
you know what you want, just forgot some little detail.
> hg also has tortoisehg, which is a very nice mature gui. There is nothing like
> that for git. I have found 1 or 2 guis that are extremely limited in function.
All Tortoise-like GUIs I have seen have a fatal flaw. They start
visualizing from the space dimension (files in the tree), then you can
dig down through the context menus to the time dimension (commits in
the DAG) and the alternate-reality dimension (branches).
Gitk (and a few less featureful lookalikes, git cola, giggle) start
with the DAG, and then you can select a commit and see which files it
touches. And this helps with the big picture immensely.
next prev parent reply other threads:[~2014-01-09 15:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 12:35 preferring mercurial Neal Becker
2014-01-09 13:11 ` Tim Visher
2014-01-09 13:53 ` Neal Becker
2014-01-09 13:44 ` Rüdiger Sonderfeld
2014-01-09 14:49 ` François Orieux
2014-01-09 17:31 ` Stephen J. Turnbull
2014-01-10 9:54 ` François Orieux
2014-01-10 11:48 ` Nathan Trapuzzano
2014-01-10 12:44 ` Stephen J. Turnbull
2014-01-10 11:50 ` Stephen J. Turnbull
2014-01-10 13:59 ` Stefan Monnier
2014-01-10 14:08 ` Eric S. Raymond
2014-01-10 15:22 ` Jordi Gutiérrez Hermoso
2014-01-10 15:55 ` Eric S. Raymond
2014-01-10 16:09 ` Jordi Gutiérrez Hermoso
2014-01-10 16:21 ` Eli Zaretskii
2014-01-11 7:15 ` Richard Stallman
2014-01-10 15:03 ` Jordi Gutiérrez Hermoso
2014-01-10 19:20 ` Stephen J. Turnbull
2014-01-10 19:54 ` David Engster
2014-01-10 19:55 ` Jordi Gutiérrez Hermoso
2014-01-11 15:55 ` Stephen J. Turnbull
2014-01-11 16:37 ` David Kastrup
2014-01-15 17:07 ` Martin Geisler
2014-01-15 16:49 ` Martin Geisler
2014-01-09 15:42 ` Yuri Khan [this message]
2014-01-10 15:16 ` Jordi Gutiérrez Hermoso
2014-01-09 20:28 ` Barry Warsaw
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='CAP_d_8W1rVOsYzQDbMxOX17540-DvTv-kgJonDLQ1-ug=q-ASg@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ndbecker2@gmail.com \
/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.