On Fri, 12 Aug 2016 18:59:37 +0200
Xen <l...@xenhideout.nl> wrote:

> > What `git mv` did is removed -- from the commit you have recorded
> > after running that command -- the file as it was known under its
> > old name and added the same contents under its new name.
> 
> Sometimes Git will recognise something as a rename if you do nothing 
> else in that commit, but if you merge the commit with something else, 
> suddenly it will not see or show it as that anymore.
> 
> For me personally too, renames are meaningful.
> 
> It's shame these renames are not detected or shown my by default.
> 
> Is there a best level approach to being more aware of any renames you 
> have done?
> 
> For a person seeing a delete and an add of the same file under the 
> different names is rather difficult to follow.
> 
> Is there an option to get Git to always track renames?

Depend on what you're asking for.

If you have asked about the `git log`, then yes: have an alias like

  git config --add --global alias.rlog `log -M -C`

If you have asked about whether it's possible to change the way Git
stores the history, then the answer is no.

As usually, I'd urge you to read an extensive overview of why Git
manages information in the way it does provided by its very creator [1].
While you certainly may disagree on the points made there and/or with
the conclusions drawn, it helps in acquiring the correct perspective: in
that text, some interesting areas are covered -- such as obtaining the
same information from several sources in an (octopus) merge or patches
-- things most of us never deal with.  What I'm leading to, is that Git
was created not as an academic project to create some idealized VC
system tailored for no particular real-world case, and implementing
whatever seemed "sensible" for a VC system to do.  Quite on the
contrary, Git is a very opininonated SCM tailored for the single
particular case: managing the Linux kernel.  The properties it gained
thanks to that goal (notably the blazing speed in the common case of
lots of small- to mid-sized files, and a set of sharp and powerful
tools) supposedly made it the most used SCM today, but it's still an
opinionated system, and it helps to know these "opinions" to understand
why it does things the way it does.  So take this text not as a dogma
to follow and praise but as an in-depth explanation of the design.

1. http://www.gelato.unsw.edu.au/archives/git/0504/0598.html

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to