[Oberon] revisions in sources; was: Project Oberon Hardware

[Chris Burrows]

I can't speak for NO but with Project Oberon (or any other source code
project that is only a few thousand lines of code) all I need is a line or
two summarising each problem that has been fixed. 

If I am interested in the detail of the code changes I keep snapshots of the
source folder(s) and use a difference listing / merge tool like Beyond
Compare (a Windows application by Scooter Software) to identify /
synchronise the code changes. 

Regards,
Chris
 
> -----Original Message-----
> From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of
> peter at easthope.ca
> Sent: Wednesday, 14 September 2016 1:58 PM
> To: oberon at lists.inf.ethz.ch
> Subject: [Oberon] revisions in sources; was: Project Oberon Hardware
> 
> Chris,
> 
> From chris at cfbsoftware.com  Thu May  7 00:19:29 2015
> > That is the intention of the *existing* Oberon Community Platform
> from ETH.
> > It has a wiki, forum etc.
> >
> > http://www.ocp.inf.ethz.ch/wiki/
> 
> Suppose that in NO, you fix a bug in one procedure.  How would you
> record that in the OCP?  Describe the change?  One or two corrections
> in a fresh installation is not a difficulty.  A few dozen corrections
> in a fresh installation is too time consuming.
>