Oswald Buddenhagen wrote: >> It might be possible to fix history for the old CVS tags later on by >> re-doing the job. > >wouldn't this invalidate all sha1s?
As far as I can tell, the trunk of SVN is fine. So that won't affect master in Git nor any SVN revision after KDE 3.4.1. Even if it weren't, the idea is to divide the repositories in two at the start of KDE 4.0 development. So the SHA-1s start over and aren't influenced by the past. We only need to fix the branches for older KDE releases and branches. That will affect their SHA-1s, but not current trunk/future master. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
