On Wed, 2010-05-26 at 21:32 +0200, Ger Hobbelt wrote: > Those [i_a] bits are my markers in our local code base so I know which edits > are mine when doing a (manual) merge with 'vanilla' CVS HEAD. Yes, I know > there are smarter systems around, but I've been 'tracking' OpenSSL for > almost a decade and tools available to me haven't always been smart enough > to ensure I didn't lose local edits across upgrades. And drilling down the > RCS database for every edit isn't fun nor fast like that. So marking has > become a habit by now. Often accompanied with a short text about the 'why' > or related info. Sorry, wasn't meant to be bothersome to you.
None of the existing CVS->git import tools handle the OpenSSL repository correctly -- they all do strange things on branches. But for HEAD, they should work OK. I'd be very happy to work on fixing that, if there's a real prospect of OpenSSL actually changing over to using such a git repository once it exists. I think that would make life a _lot_ easier for anyone working on OpenSSL. Git is portable enough, and a git server can offer cvspserver access for users who are resolutely stuck in the 20th century. -- dwmw2 ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
