From: Jeff King <peff@peff.net>
To: Stephen Smith <ishchis2@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Stephen Smith <ischis2@cox.net>
Subject: Re: Is the a way to get a log with files that were changed
Date: Thu, 11 Sep 2014 22:26:01 -0400 [thread overview]
Message-ID: <20140912022600.GA15519@peff.net> (raw)
In-Reply-To: <FD6D2EE2-AD97-4D40-B461-435FD18D7E1A@gmail.com>
On Fri, Sep 12, 2014 at 07:16:26AM +0530, Stephen Smith wrote:
> Is there a way to get a log of first parent commits and with each
> commit a entry a list of the files that were changed?
How about:
git log --first-parent -m --name-only
The "--first-parent" restricts the traversal. The "-m" tells git to show
merge diffs against their parents. We show only the diff against the
first parent due to "--first-parent", so we effectively show the diff of
what was brought in by the merge. And then "--name-only" can be replaced
with "--raw", "-p", or whatever diff format you prefer.
-Peff
prev parent reply other threads:[~2014-09-12 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 1:46 Is the a way to get a log with files that were changed Stephen Smith
2014-09-12 2:26 ` Jeff King [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=20140912022600.GA15519@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=ischis2@cox.net \
--cc=ishchis2@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.
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).