linux-kernel - git mv (was Re: [git pull] ACPI & Suspend patches for 2.6.29-rc0)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 09 Jan 2009 15:56:57 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org,
	Linux Power Management List <linux-pm@...ts.osdl.org>
Subject: git mv (was Re: [git pull] ACPI & Suspend patches for 2.6.29-rc0)

> As usual, git is actually smarter and get things more correct than people 
> realize. What you found "surprising" is actually a "profound truth". 
> 
> Git is like a great indian mystic. It sees past the veil of the trivial, 
> to find the true connections in life.
> 
> Or at least in source code.

Thanks for confirming that the unexpected diff
is a fature of git rather than a bug.

Since I had used "git mv", I had expected everything
to show up as a move.  However, I understand that
comparing file contents over that move and other code moves
told a different 'big picture' story.

I guess using 'git mv' gave me the false expectation
that git actually tracks moves like other SCMs
and it would show up that way in the diff -- though
now that I think about it, I like the comparison
of the two endpoints that git did even better.

I guess you can make an argument either way about
how to handle moves.  One problem that both have to
deal with is that a history on the old (now missing)
file location doesn't work, and that by default
the history on the new location stops unless 
log --follow is used.  gitk doesn't use --follow
by default, and when it is added, the history
looks pretty strange.

thanks,
-Len Brown
Intel Open Source Technology Center

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/