From: Scott Chacon <schacon@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Pro Git Book
Date: Tue, 28 Jul 2009 09:14:27 -0700 [thread overview]
Message-ID: <d411cc4a0907280914v520d3c25xefc4e0f74046c4bb@mail.gmail.com> (raw)
In-Reply-To: <20090728085600.GA33224@gmail.com>
Hey,
On Tue, Jul 28, 2009 at 1:56 AM, David Aguilar<davvid@gmail.com> wrote:
>
> Good stuff,
> Thanks Scott.
>
> In http://progit.org/book/ch7-1.html we go through a
> lot of machinations to setup an external diff viewer.
>
> That might be a good time to introduce git-difftool, even if
> only to mention that the setup is much simpler when difftool is
> used. It allows you to do without the wrapper scripts.
>
> $ p4=/Applications/p4.merge.app/Contents/MacOS/p4merge
> $ git config --global difftool.p4.cmd "$p4 \"\$LOCAL\" \"\$REMOTE\""
> $ git difftool -t p4
>
> $ git config --global diff.tool p4
> $ git difftool
>
> It's even easier if you use one of the several built-in tools,
> e.g. opendiff, kompare, meld, etc., since it requires no
> configuration.
That's a good point - I never actually covered that, it looks like.
I'll put that in the list of things to cover for the second edition :)
>
> Mentioning that it's a fairly new feature is probably important,
> too. Hmm. I guess I should've send a patch ;-)
If you are interested in contributing and don't mind releasing the
rights to your contributions to also be published commercially under a
second edition in the future, please feel free to fork the project on
GitHub and send me a pull request for anything you add. I've already
gotten errata in this manner, which is pretty cool. Otherwise I'll try
to get this in eventually.
Thanks,
Scott
next prev parent reply other threads:[~2009-07-28 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:56 Pro Git Book Scott Chacon
2009-07-27 21:16 ` Tim Visher
2009-07-28 8:56 ` David Aguilar
2009-07-28 16:14 ` Scott Chacon [this message]
2009-07-29 9:34 ` Jakub Narebski
2009-07-29 15:38 ` Scott Chacon
2009-07-29 18:30 ` Sverre Rabbelier
2009-07-30 15:51 ` Luciano Rocha
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=d411cc4a0907280914v520d3c25xefc4e0f74046c4bb@mail.gmail.com \
--to=schacon@gmail.com \
--cc=davvid@gmail.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).