From: Martin Langhoff <martin.langhoff@gmail.com>
To: _g e r r y _ _l o w r y _
<gerry.lowry@abilitybusinesscomputerservices.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: if YOU use a Windows GUI for Git, i would appreciate knowing which one and why
Date: Wed, 1 May 2019 14:42:42 -0400 [thread overview]
Message-ID: <CACPiFCL0UZv6WBMq3ZdrGE6bWNGLye22xEWUadneB8gzTAOzsA@mail.gmail.com> (raw)
In-Reply-To: <1b8a01d47466$9775c130$c6614390$@abilitybusinesscomputerservices.com>
On Sun, Nov 4, 2018 at 2:34 PM _g e r r y _ _l o w r y _
<gerry.lowry@abilitybusinesscomputerservices.com> wrote:
>
> [1a] Which do you prefer: Git GUI, Git command line?
git cli
>
> [1b] What is your reason for your [1a] preference?
I'm a cli guy, I know git well, and it gives me all the power.
However, understanding history/branch structure is not something you
can do well with the cli tools (git log has an ascii art branch mode
that works for some situations).
For a number of reasons, I often find myself looking at new codebases,
and wondering how they got to where they are. Visualizing and querying
history is a killer feature for me.
> [2a] if applicable, which Git GUI do you prefer?
gitk ; if not available, whatever I can install quickly that (a) I can
just start in a checkout and (b) has a good branch history view. In
other words, the more they resemble gitk the more I like them :-)
> [2b] What is your reason for your [2a] preference?
Best for navigating history, complex branch/merge patterns. Handy
search including pickaxe.
It doesn't support the "normal" workflows. It's just an outstanding
complement for the cli tools.
cheers,
m
prev parent reply other threads:[~2019-05-01 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 17:48 if YOU use a Windows GUI for Git, i would appreciate knowing which one and why _g e r r y _ _l o w r y _
2018-11-05 12:26 ` Philip Oakley
2019-04-28 9:33 ` David Aguilar
2019-05-01 18:12 ` Jakub Narebski
2019-05-01 18:42 ` Martin Langhoff [this message]
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=CACPiFCL0UZv6WBMq3ZdrGE6bWNGLye22xEWUadneB8gzTAOzsA@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=gerry.lowry@abilitybusinesscomputerservices.com \
--cc=git@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).