* Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net [080126 01:50]:
- causes lots of breakage when you try to go back to versions before the
rename (try it with coreboot v2!)
Tried it, worked fine for all renamed files and directories. Are you confusing this with CVS, maybe? I suggest http://svnbook.red-bean.com/ for all people with problems regarding the repository.
- introduces inconsistencies in at least half of the patches (some
references to LB are changed, some remain)
What you call inconsistencies was done on purpose. Renaming the LB_ defines used for the coreboot table would break all payloads using that information out there. That's a no-go.
Like any other open source project, coreboot is a living project that is being worked on. The fact that changes happen gradually and incrementally is nothing inconsistent. We did not break any boards with them either. It seems you are not content with the way we renamed the project, but your hints are kind of vague. Those that we could read between the lines were taken into regard (I hope). Please help us get the rest fixed.
Sorry Uwe, this is not against you. I have been working with the trees a lot in the past two weeks and the v2 rename has broken "svn up" to older versions, svn blame gets interesting etc. Right now I'm working with multiple trees, some in a state before the rename, some after the rename and tracking down when some problems were introduced requires me to switch trees constantly. That makes me really grumpy. If I could go back in time, I'd stop the whole tree moving/renaming. Project renaming is OK, but tree renaming is a real pain.
Try following the hints I sent to the list on how to upgrade the tree. These helped me migrate over a dozen trees in different states with nearly no conflicts. It's really trivial in most cases.
Stefan