Hello Andrew!

Sunday March 17 2019 00:11, you wrote to me:

 > Hello Vince!

 > 16 Mar 19 18:44, you wrote to all:

 VC>> Above version is released and hatched in MBSE_BBS.
 VC>> Also available on SF within file group 1.0.7.

 VC>> This reflects the code base at least on CVS as amendment
 VC>> 1.0.7.11B is not present on git or Hg.

 > Sourceforge has discontinued active use of CVS; I believe your changes
 > are in the SVN repository on Sourceforge.

 VC>> This change and the latest is as follows as shown in Changelog
 VC>> but note that this only covers changes for 2019 and
 VC>> Changelog_2018 covers 2008 - 2018 : @Andrew you might want to
 VC>> update git and hg versions.

 > I will update them tonight hopefully.  Going forward, I think we need
 > to select a single source code management solution, to avoid having
 > multiple repositories that need to be kept in sync with each other.

 > I've primarily been using Hg, as that's what Michiel was using before
 > I got into this project.  I believe that Jame was using Git in his
 > Debian packaging work.  You have started using SVN recently.


I simply can not get git to work for me - OK, I cannot find the commands and 
subcommands to
:



 > I propose that at the next major release (1.1.0?) we drop updating the
 >  redundant repositories and all switch to using the same one.  My
 > personal inclination is to use Git, but if there's a reason you prefer
 > to use SVN, I'm all ears.

Opps, Correct I am using SVN.

Just above cannot work out how to :

add and delete (new and old files) (svn add and svn del)
update my local folder with the current contents on SF (svn update)
Run a diff against as above (svn diff)

then
commit (svn commit -m "Reason for update etc "

Should point out that hg is hardly main stream.

and yes the next update should show as 1.0.8 it is about due !


Vince

--- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715