Olin Lathrop wrote:

> To get the nice documented history of each module, see which versions
> of each file were used to produce what versions of executables when,
> etc.

And to know what was changed for what purpose without cluttering up the
code with comments.  For example:

https://github.com/jjmcd/Elmer160/blame/master/LCDlib/LCDinsc.asm

and you can see what commit is "blamed" for a particular line.

If you wonder what other files were affected by that same commit, click
on, for example, eedde787 (the "All code in named section" commit happens
to have affected a number of source files) and you will see all the files
touched by that commit, and below that list the differences in each file.

When you go back to grab some old code, or even when you are pulled awy
from a project for a while, it can be hard to remember these things.

--McD


--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.