From: Jonathan Tan <jonathantanmy@google.com>
To: Aleksey Bykov <aleksey.bykov@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: The original file that was split in 2 other files, is there a way in git to see what went where?
Date: Tue, 23 Jan 2018 08:32:00 -0800 [thread overview]
Message-ID: <CAGf8dg+XPPrx+Fv5d2hTgBMyWDBavFvOmXzJiX+8PuHBSoUCrw@mail.gmail.com> (raw)
In-Reply-To: <CAMAMitC-iyH_YOAsJcPpLcUbmX-Zun4MCL89Pxn2rr7Lu_m2cQ@mail.gmail.com>
On Mon, Jan 22, 2018 at 7:22 PM, Aleksey Bykov <aleksey.bykov@gmail.com> wrote:
> Is there an easy way to see:
>
> 1. what came to b from a?
> 2 .what came to c from a?
> 3. all extra changes apart from just moving stuff?
One way to do this is to use "--color-moved" - it will tell you what
in b.txt and c.txt was moved and what wasn't (although it won't tell
you from where). This was introduced recently, I think in 2.15.
next prev parent reply other threads:[~2018-01-23 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMAMitCV3xvaSr00H574Pww=r_c3=0NqT1Ge13kc=gWJqDJ3Ug@mail.gmail.com>
2018-01-23 3:22 ` The original file that was split in 2 other files, is there a way in git to see what went where? Aleksey Bykov
2018-01-23 16:32 ` Jonathan Tan [this message]
2018-01-23 16:55 ` Jeff King
2018-01-23 18:37 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGf8dg+XPPrx+Fv5d2hTgBMyWDBavFvOmXzJiX+8PuHBSoUCrw@mail.gmail.com \
--to=jonathantanmy@google.com \
--cc=aleksey.bykov@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).