This is a heads-up regarding replacing the main Pike git repository with a filtered copy.
The main reason why we'd want to do that is that there is a syntax error in the timestamp fields of the commit objects, causing "git fsck" to complain about most commits. In order to fix that, I have run "git filter-branch" on the repository, performing transforms on the commit objects to fix the timestamp issue, but also fix some other issues which ought to be addressed if we are doing a filtering anyway. These include replacing some obsolete email addresses, as well as removing empty commits and fixing some whitespace issues. See http://pike-svn.lysator.liu.se/twiki/bin/view/Main/RepoFilter for a complete list of changes made to the repository.
Please look through the list of changes, and if there is something which should be added or removed, please say so. A filtered version of the current repository can also be examined at git://pike-git.lysator.liu.se/pike-filtered.git.
If there are no objections, we could declare a flag-day (say, next Saturday) when the filtered repository replaces the current one. Of course, a new filtering would then be performed so that any commits made after today are also included. It would make things simpler if no new commits were pushed during the 5 hours it takes to run the filtering operation though.
If the repository is replaced with the filtered version, it means basically that all commits get new SHAs. If you have local branches tracking the upstreams branches with rebasing, performing a "git pull" should be able to sort things out automatically. However, if you have non-tracking branches they may need to be rebased manually. When all your work is rebased on the new repository, running "git gc" to get rid of the old duplicate commits is recommended.
Questions and comments are welcome.