On Friday 16 October 2009, Øyvind Harboe wrote: > > I have a tree that removes those commits plus a few other bits > > of noise that crept in. Thing is, pushing it would NOT be enough > > to achieve the full cleanup. The existing clones would need some > > cleanup/updating... > > Do you have a description of your changes?
See the appended graft file ... note that we can't quite just stuff this in the git repo on sourceforge. That will result in broken "git log" output, though it does make the pulls be gratifyingly small. > Could you email me the repository directly. Don't want to dump 5mByte > into the mailing list, but my mailbox won't mind! I'd rather just push a *single* version of the tree, next week. You can create the equivalent, using the latest tree and the appended "grafts" file. (Total tree size ~17 MBytes after scrub, vs ~113 MBytes before.) > We should perform this cleanup before 0.3. It would > be nice to review the cleanup and get the servers > updated next week sometime. > > Review + a day's notice during the working week is called > for here... So, how about I do the switchover on, say, Tuesday? - Dave # see http://git.or.cz/gitwiki/GraftPoint # # install in .git/info/grafts and see "git filter-branch" re how # to quickly rebase without these commits. then clean garbage # from the resulting tree. # ~100 MBytes of snapshots 81ba80d742d8e422b9a3fdcbdf4713959e5852ad 5c01a21b643348d1022b72274778b395638e981b # annoying "testing ssh access" rebase commits 97718b2e3ede522b05fe80b2e75d785920f9f088 0230ed40ed537bdd30c39340b76b736cf553807b 95fb11ce7329a744506e1777fbb15c1b25e03bb8 95fb11ce7329a744506e1777fbb15c1b25e03bb8 61e5fb6c020c90d43393e925a750b3bf3b07be95 b54504de6e95fda3abf9452dd4e3b1f8e4eb522e b54504de6e95fda3abf9452dd4e3b1f8e4eb522e a58e6e4739cbaeea5eef52035baa376f449095ce 4ae1ff0167a82655c72b3aa78297ddd3f219ee4d 7191a4f2487ef11c58a3364cdc240e259d55a92e 86727fe1855b5e51f25cab640c7ec2b9dc126e6b 1fa3c2ff3201929e6610f310267f65977585a7ca 4ae1ff0167a82655c72b3aa78297ddd3f219ee4d 13852e5daa53e9b141e7bb42adc47c53f342015c 347b8f901e15b9eae94b363afda0429313a58807 347b8f901e15b9eae94b363afda0429313a58807 083fd58f3767647a025f92b4de1c31e4703ac0c2 7191a4f2487ef11c58a3364cdc240e259d55a92e _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
