[Olsr-dev] Possible to fix errors in git repo?

[Henning Rogge]

> the way to fix this is to export and re-import the entire tree.
> however, every commit id will change, which is kind of not-so-nice since
> the tree is public

I did some tests with a number of local trees and noticed another problem.

I imported the olsr.org tree (to have a "olsr.org repository" to experiment 
with), then cloned it locally.

I then replaced the content of the local olsr.org repository with the fixed 
content from Aaron Daubmans github repository... no fsck errors anymore there.

Then I pulled from the cloned client... git did it without a warning, and did 
a merge with the new stable branch.

This means the client repository now contains the good AND the bad commits.

When the client pushs, the bad commits are inside the olsr.org repository 
again!

Henning Rogge
-- 
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961,   Fax +49 228 9435 685
mailto:(spam-protected) http://www.fkie.fraunhofer.de
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20110615/9ec8bee5/attachment.sig>