> On 7 Oct 2019, at 15:06, Daniel Gruno <humbed...@apache.org> wrote:
>
> On 06/10/2019 17.59, Nick Kew wrote:
>>
>> OK, I've just dug up an example in an Apache/Github project. A simple
>> renaming
>> of a source file, that with "svn mv" would have preserved history, seems to
>> have
>> essentially wiped its past. 'History' is highly misleading, 'Blame' is 100%
>> wrong!
>
> It would be 100% wrong in svn as well if the same operation had been
> performed there, as it wasn't a move - the number of lines don't match up.
> There is a `git mv` just like `svn mv` that preserves history, AIUI. A file
> where `svn mv` was actually used [1] shows that the history is preserved
> through the mv operation and blame works as intended, even in git.
Which points to another problem. The committer concerned wasn't a git newbie,
he's been happily using it for (I know not how long) before the project ever
came
to Apache. And I can't believe the renaming was malicious.
So why did he get it wrong in this manner? Perhaps it points to the real-life
complexity of git, and its real-life consequences?
I've got caught on that myself (in a non-Apache context) before: things like
git merge of a branch having spectacularly unintended consequences for
what history subsequently looks like.
Indeed, perhaps the cause of the screw-up wasn't really the renaming, but some
subsequent change whose author had never even looked at the source file in
question?
If you look at history, many of the changes there seem to be mass
formatting-exercises.
The line count appears to be an artifact of the committer's toolset, which
includes
some auto-formatting such as
-extern "C" void TSPluginInit(int argc, const char *argv[])
+extern "C" void
+TSPluginInit(int argc, const char *argv[])
> As Eric alluded to, it's much less about svn versus git than it is about
> tapping into the community on GitHub. If there was an svnhub, I'd be all for
> that as an easier way to do this, but alas no.
So the Apache community isn't good enough and we need Microsoft?
OK, that's not quite fair. But isn't that what the github mirror is for?
--
Nick Kew
