Hello All!

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

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

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

--
v1.0.7.12 15-Mar-2019 - Andrew Leary

1. MBCICO will no longer leave partial files in the temporary
inbound when a remote Binkp site attempts to send a zero byte
file. An M_GOT message will be sent to remove the zero byte
file from the remote's queue.

2. Fixed the bad/orphan .TIC file support to handle .TIC files
with names longer than 8 characters.

3. Updated copyright notices to 2019.

v1.0.7.11B 22-Jan-2019 - Vincent Coen

1. This patch a simply adds /usr/pkg/include and /usr/pkg/lib to the
configure.ac file, enabling the proper detection of libGeoIP and libbz2
on NetBSD systems. The reason for this change is that for a time now,
NetBSD uses /usr/pkg as the path for all libraries, binaries and other
content installed through the pkg_add command or the pkgsrc installation
tree. That way we keep the files and programs provided by the core
system separated from user installed packages.

2. Update CP to 2019.
--




Vince

--- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Vince!

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

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

This reflects the code base at least on CVS as amendment 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.

This change and the latest is as follows as shown in Changelog but
note that this only covers changes for 2019 and Changelog_2018 covers
2008 - 2018 : @Andrew you might want to 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 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.

Andrew

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

On 17 Mar 2019, Andrew Leary said the following...

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.

I would love it if SF was ditched and this moved to Github. (Its only a personal preference - I find github so much easier/faster to use than SF). I too would then be able to use my backend tools to automate builds (and if it time permits push up some updates to review).

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)

Hello Andrew!

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

Hello Vince!

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

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

This reflects the code base at least on CVS as amendment
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.

This change and the latest is as follows as shown in Changelog
but note that this only covers changes for 2019 and
Changelog_2018 covers 2008 - 2018 : @Andrew you might want to
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
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)