Re: How to keep log history when renaming and changing simultaneously

From: Urs Thuermann <urs@isnogud.escape.de>
Date: Apr 17, 2017, 21:36 UTC
Message-ID: <ygfefwqzph7.fsf@tehran.isnogud.escape.de>
In-Reply-To: <f456df1f-cda2-4681-8f01-b693655e79a7@gmail.com>

Igor Djordjevic <igor.d.djordjevic@gmail.com> writes:

Show 6 quoted lines

> For both cases (renaming and splitting), would using `--find-copies` 
> work for you? Perhaps with some low threshold value to start with, if 
> the default one yields no results.
> 
> If interested, adding `--name-status` to the mix will show similarity 
> percentage between old and new file(s).

I didn't know --find-copies and --name-status and I've now looked them up in the doc. Looks interesting but instead of looking for similarity it would be better IMHO if there was a command "git cp" and that "git mv" and "git cp" were recorded in the history somehow.

I'm still using CVS (and SVN in some few cases) but considering changing to git. There are some things, however, that I can do more easily in CVS (like editing CVS ,v files instead of git commit --amend) and I need to learn more git before I want to change (and migrate existing repos).

urs