> On 6 Oct 2019, at 04:06, Daniel Gruno <humbed...@apache.org> wrote: > > On 05/10/2019 19.30, Nick Kew wrote: >>> >> If it moves to github, how and at what level is history preserved? Github >> can do >> alarming things with history even for a project that's always been there! > > We would have the exact same level of history as before (one might even say > we'll get more history, as you can specify committer and author separately in > git). If you look at https://github.com/apache/httpd which is our current git > mirror, it should have the exact same commits going back to 1996 as the > subversion repository. There is a bit of a lag on the mirror right now, but > that is a separate issue that will be fixed on October 12th.
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! https://github.com/apache/trafficserver/blob/master/plugins/experimental/stream_editor/stream_editor.cc And that's within git: no actual change-of-repos involved. Regarding httpd, we have the git mirror, so access is available through whatever a contributor prefers. How is that not best-of-both-worlds? -- Nick Kew