No one complained for a week, and all votes seemed to be in reasonable favor
of Mercurial so Mercurial it is.
I've created the Mercurial repository and imported the subversion repo
history into it from revisions 1 to 1703.
To avoid having people accidentally commit additional code to the subversion
repo, I've disabled all but read-only access to everyone.
You'll find a new Mercurial link at the top of the sourceforge.net project
page. Please use one of the following command lines to check out a mercurial
work area:
For ssh access:
hg clone ssh://jcalc...@hg.code.sf.net/p/openslp/mercurial openslp
For https access:
hg clone https://jcalc...@hg.code.sf.net/p/openslp/mercurial openslp
Https access is purported by SF staff to be a bit slower than ssh, but for
ssh you'll probably need to add a public key to your profile if you haven't
already done so.
I know it's customary to use an email address when committing to a DVCS, but
I'd like us to continue to use our sf.net user ids so there's some
continuity between the original repo and new commits.
If you've never tried it before, look at TortoiseHG - it's a QT-based qui
tool that really gives you a nice view of the repository. And it can make
some operations on your local work area much easier than the command line.
It's also portable between windows and linux (I have versions of it
installed on both my windows and linux machines).
Thanks,
John
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Openslp-devel mailing list
Openslp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openslp-devel
