One reference I like, for working with git, is: http://marklodato.github.io/visual-git-guide/index-en.html
A bit of time studying that page should give you a somewhat decent understanding of its core concepts. (A perhaps related hint is that its internal structure bears some strong simularities to that of unix filesystems, but with content hashes replacing inode numbers. ...but maybe that only helps people who understand unix filesystems...) -- Raul On Tue, May 17, 2016 at 7:41 PM, <[email protected]> wrote: > Do folks want me to make suggestions how to make better commits to the > J source repository? > > Doing proper write-ups what's sub-optimal and what to do instead would > take a lot of my time, so please let me know if you'd be interested in > constructive criticism at all. Eric? Bill? Henry? > > Simple changes how commits are done would go a long way. My suggestions > would refer to better git usage or coding style. > > > Job credentails: > > I have three decades of open source coding under my belt, > (Whenever you are using any of gcc, gdb, emacs, vim, or cvs, > you are actually running my code, too :-) > > I am also inherited enough Original German Bluntness genes > to do this job. > > Martin > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
