Thanks for letting us know, removed the note about `git mv` Was left over from svn notes, since git has a move command, it was left in.
On Sun, Dec 28, 2014 at 8:25 PM, Julien RIVAUD (_FrnchFrgg_) <frnchf...@free.fr> wrote: > Le 27/12/2014 23:07, Campbell Barton a écrit : >> Updated wiki docs based on feedback. > > One remark about the Git Usage section: > > TL,DR: no need to require "git mv" to move files, thing will work > exactly the same without. > > Requiring developpers to use git mv doesn't make sense at all since git > doesn't store any information as to where some piece of code comes from, > contrary to all other VCSes that I know of. (git mv is just a shortcut) > > Instead, git always stores the full tree for each commit (and the > storage is efficient because it is content-adressed and deltafied after > the fact). > > BUT, git uses heuristics to recover file movements when requested. It > has two upsides: > > - If you don't git mv but move files in your explorer and git add -A, it > doesn't matter > - git can detect partial files moves, or file merges, and preserve > history for a single *function* that moved several times across several > files. No other VCS does it AFAIK. > > Julien "_FrnchFrgg_" RIVAUD > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers