> On Aug 6, 2019, at 12:32 PM, Maxim Kuvyrkov <maxim.kuvyr...@linaro.org> wrote: > ... > I've setup uploads and updates of fully converted GCC history (all branches > and all tags) in 3 flavors. These will be updated roughly hourly. > > 1. https://git-us.linaro.org/people/maxim-kuvyrkov/gcc-pretty.git/ > This is a fresh conversion from scratch with "pretty" authors. > > 2. https://git.linaro.org/people/maxim-kuvyrkov/gcc-mirror.git/ > This is a close match to current GCC mirror. Trunk and gcc-*-branch branches > are imported from the mirror, and the rest is reconstructed starting from the > imported branches. > > 3. https://git-us.linaro.org/people/maxim-kuvyrkov/gcc-raw.git/ > This is a fresh conversion from scratch with no author rewrites. >
The conversion is now fully complete. The above 3 repositories all have complete and accurate [1] history of all branches and tags. SVN's /branches/* are converted to Git's refs/heads/*, and SVN's /tags/* are converted to Git's annotated tags refs/tags/*. SVN's /trunk is Git's refs/heads/master. I propose that we switch to gcc-pretty.git repository, because it has accurate Committer and Author fields. Developer names and email addresses are extracted from source history, and accurately track people changing companies, email addresses, and names. IMO, it is more important for people to get credit for open-source contributions on github, ohloh, etc., than the inconvenience of rebasing local git branches. It's also an important marketing tool for open-source companies to show stats of their corporate email addresses appearing in git commit logs. I also suggest that we don't wait for Cauldron to make plan on when and how to switch. I believe the big decisions should be made on the mailing list, and at Cauldron we can discuss finer points. [Also, unfortunately, I won't attend this year.] [1] Gcc-mirror.git has artifacts in several commit messages due to edits of SVN commit messages after the fact. Regards, -- Maxim Kuvyrkov www.linaro.org
