- changed status to resolved
Manual CVS file manipulation resulting in forced git history update
Issue #2
resolved
Sometimes after the commit:
commit 442961ae990019740c1d5c51fcecd31a7d5898cb
Author: ragge <>
Date: Mon Mar 7 02:00:02 2016 +0000
new date 20160307
The file mip/compat.c is moved to create common/compat.c,
and this affected the history for a whole lot of files
starting with this commit (in old-* branches):
commit 5452cef558bab66135b929f4d064054a16d3d285
Author: ragge <>
Date: Thu Sep 20 12:52:15 2007 +0000
Oops, forgot this one.
diff --git a/mip/compat.c b/mip/compat.c
new file mode 100644
index 0000000..7050888
--- /dev/null
+++ b/mip/compat.c
Which is now:
commit 616996becf53088703a3fa89896c395a888f922f
Author: ragge <>
Date: Thu Sep 20 12:52:15 2007 +0000
Oops, forgot this one.
diff --git a/common/compat.c b/common/compat.c
new file mode 100644
index 0000000..7050888
--- /dev/null
+++ b/common/compat.c
Comments (1)
-
repo owner - Log in to comment
Git master and all release branches forcibly updated. Sorry for any inconveniences.