andreas pålsson andreas.palsson+open...@gmail.com wrote [2011-10-18
05:29+0200]:
I though if you could see how it looks and feels like with a modern
VCS, it could help you decide if migrating is worth it.
git://pubgit.metux.de/mirror/openssl.git
Wishes,
--steffen
Hello.
I was poking around in the source code earlier, thought it could be an
interesting experiment to convert the repository to Mercurial.
It seems to have worked quite good, tags and branches seem intact. :)
I put up a read-only copy here; https://bitbucket.org/apalsson/openssl/
I though if
-control-system-per-child craze
Some of the members of the team do work for google. To my best
understanding google is internally using mercurial so this discussion is
actually not concluded. Hence the project will stay in the 20th century
until a new version control system is agreed upon.
I would
with _any_ project which uses a legacy
version control system (cvs,svn,hg,bzr,etc) is to mirror it into git so
that I can deal with it sensibly. OpenSSL has so far resisted my
efforts, which is one of the reason I find it a PITA to deal with.
The state of the test-repository is a bit old (approx
to decide? Are there any plans being seriously proposed other
than
1) Stay in the 20th century with CVS as we are now.
2) Update to git.
Surely nobody's suggesting svn/bzr/hg/arch or any of the other artifacts
of the one-version-control-system-per-child craze?
--
dwmw2
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
last tested.
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.
Internal discussion about which version control system
, they
should work OK.
So far we have not seen technical problems when last tested.
That's interesting. What tool were you testing? I've had issues with
both cvs2git and git-cvsimport.
My normal reaction in dealing with _any_ project which uses a legacy
version control system (cvs,svn,hg,bzr
