I've been thinking about attemtping to refactor g.Git functions for some 
time, or at least organized them by type, but haven't come up with a plan 
for how. (I haven't been able to follow the complete path Leo takes to 
calculate it's version.) The g.Git functions are a mixed bag of "requires 
git executable in PATH", "only needs .git folder (and contents)", and 
"really about GitHub not Git".

The 3 functions related to determining Leo version number are:

   - g.gitInfo() uses file system - returns: branch and commit hash.
   - g.getGitVersion() requires git exe - returns commit: author, hash, 
   date-time
   - g.gitDescribe() uses git exe - returns: git tag, distance-from-tag, 
   and commit hash
   
Strictly speaking for Rob's opening scenario we don't need to use git exe.

-matt


-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/17eac399-3458-41ad-bf2b-8b2e1895d5d0%40googlegroups.com.

Reply via email to