From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Peter Toye <git@ptoye.com>
Cc: git@vger.kernel.org
Subject: Re: A puzzling omission from the Git book
Date: Fri, 29 Mar 2019 09:04:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1903290903430.14340@localhost.localdomain> (raw)
In-Reply-To: <373066205.20190329125548@ptoye.com>
On Fri, 29 Mar 2019, Peter Toye wrote:
> I'm looking for a way of comparing the files in two branches.
> According to Stack Overflow there's a git diff command but I can't
> see any reference to it in the book. Am I being more than usually
> thick?
it should be just
$ git diff <branch1> <branch2> -- <filename>
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2019-03-29 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 12:55 A puzzling omission from the Git book Peter Toye
2019-03-29 13:04 ` Robert P. J. Day [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=alpine.LFD.2.21.1903290903430.14340@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@ptoye.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).