Arv,
Being an anarchist by nature, I wing it.
Before making changes, I save to a zip archive of everything I care about, named perhaps ubitxjg37.zip
Then I create a new header at the top of the main file with the date, perhaps ubitxjg38:? 2018-6-4
and add comments below that header as I adjust the code.?
When I'm ready for other people to look at it, I review all those comments and make sure nothing
is still outstanding, then remove all of it, leave only comments that are current.
Call the whole thing revision 1.0 and send it out.
Never have really figured out git in a serious way.
Don't intend to.
? ??
Jerry, KE7ER? ?(just now up from his nap)
toggle quoted message
Show quoted text
On Mon, Jun 4, 2018 at 03:17 pm, Arv Evans wrote:
As I get even older I find that some sort of revision control system is needed in order
to do any code work.? I use CVCS on Linux to tell me when I last worked on a coding
project, what changes I made at that time, and then check-out the latest version for
continued work.? I can remember code I wrote at Bell Labs in 1980, but not what I
wrote for my Raduino last week.? Getting old is difficult and frustrating.? 8-(
