On a sunny day (Tue, 7 Aug 2018 12:08:55 +0000 (UTC)) it happened Martin
Gregorie  wrote in :

>On Tue, 07 Aug 2018 10:40:33 +0000, Jan Panteltje wrote:
>
>> I use a backup script per program code I work on.
>> You can use cp -urp if you want recursive.
>>
>The best way to avoid losing source code, scripts, web pages, etc is to
>use a version control package in addition to conventional backups.
>
>I generally use CVS but am also using git for a couple of projects.
>
>CVS is quite old now, but has two advantages:
>
>- its source repository is always separate from the source code. It may
>  be in a different user on the same host, but it can equally be on a
>  separate server on your LAN
>
>- everybody commits to the same repository
>
>- as the repository is a mirror of your source tree, it can sometimes be
>  convenient to go in as the CVS user and modify it with cp, mv and
>  friends or to edit source files (these contain the original source
>  with sets of comment+changes appended for each commit
>
>git seems pretty good, but:
>- its repository is a large, opaque file structure in the root directory
>  of the source tree, so if it does wrong you're stuffed.
>
>- you can, however, push the local repository to update a remote one (on
>  github or your own server) and pull a fresh update from the remote
>  repository followed by an update to bring your source tree into line
>  with the local repository.
>
>Both have the advantage that, if you completely screw up an edit, you
>just delete the wrecked file and run an update, which pulls the latest
>version out of the repository.
>
>In both version control systems, if its a shared project you need to run
>an update to pull down the latest commits before editing anything ('cvs
>update' for CVS and 'git pull; git update' for git.
>
>I've been using version control systems for over 3 decades and would not
>dream of writing code, scripts or web pages without using version control.
>
>My local CVS repository is on my house server and is used for all
>projects regardless of whether they are developed on the server, one of
>my laptops or my Raspberrypi.

Yes, I am aware of those systems, sometimes I look at code, sometimes I
download things.
Maybe my ego or way of coding is not suited for multi-contributing coders..
Last time somebody emailed me with some ideas causing me to re-write some code
his way,
after some back and forward emails finally got to the point where he said:
'Why do you not do it that way', to which I replied 'That was the way the
original was done'.
I do not always say 'why' (almost never actually) I write code in some way,
most is based on small tests and incremental code.
Gets complicated and hard to follow it seems for others...
So what I do is use scripts, when I think I have tested enough and it MAY be of
use to others,
I just run a script called
to-web version_number
from the coding directory
and that puts it on my website.
After that I update the VERSION define, and all version references in the
documentation.
The program-xx.tgz is the release and also my backup.
It is then on a US server, my own server, and later on my backups.
Here a screen shot of the current working directory of a very simple program I
released as 'weather_sensor-0.2.tgz'
a while ago:
 http://217.120.43.67/nuclear/ws.gif

Not even on the main web site yet, only on the raspi server as
 http://217.120.43.67/nuclear/weather_sensor-0.2.tgz
bks is the backup script,
to-net is the script that makes the ..tgz and sends it to the website
and test1 is how I tested the code (command line option etc).

I have some programs on some other sites, like this one that reads data from
seven segment displays
 http://panteltje.com/panteltje/newsflex/download.html#7s_parser

But almost all public releases are at this link:
 http://panteltje.com/panteltje/newsflex/download.html

Some programs are thousand of lines of code, I would not want anyone else
changing one character anywhere in it :-)
It could make it better, or worse, but would break my view, oversight.
Several times I just gave the advice: Split it off under your own program name.
And so it happened.
Saves me answering a hundred email questions about things.

That is an other aspect, cute, sometimes I get a bug report about code I wrote
20 years ago.
If it is justified I fix it make a new release.
Happened some month ago.

--- SoupGate-Win32 v1.05