Bill,
Thank you so much for the explanations below...it cleared-up a number of
misunderstandings on my part. I believe that I am in "business" now as far as
completing the builds and understanding the rresults.
Ed, K0KC
[email protected]http://k0kc.us/
On Monday, July 9, 2018, 7:24:25 PM EDT, Bill Somerville
<[email protected]> wrote:
Hi Ed,
some comments in line below.
On 09/07/2018 16:59, Ed Wilson via wsjt-devel wrote:
I have enjoyed building and testing WSJT-X developmental releases over the
past few years and would like to continue to do so. I understand that the move
to GitHub has required some changes to the JTSDK build process and I have
followed Greg Beam's excellent instructions and have successfully built the
application. A build today (7/9/2018) results in WSJT-X 1.9.2-devel with a
number 308245 in the "About WSJT-X" screen. May I assume that the number 308245
(in this case) is a build number which will increment as commits are
implemented by the developers (similar to the previous release number)?
The WSJT projects have not moved to GitHub, they are still hosted on Source
Forge but we have migrated from the Subversion version control system to the
git distributed version control system. Source Forge allows projects to use
either system. The git DVCS offers many benefits to the development team, some
of which solved some immediate and pressing issues, hence the switch.
Because of the distributed nature of git there is no entity that can oversee
any sort of incrementing revision number and because git also allows more
complex branching and merging change history, the concept of such a revision
number would make no sense anyway. Instead git forms an unique hash code
derived from the state of the sources, the commit comment, the author's
identity, the timestamp of the commit and the parent commits of the commit.
This hash code is a SHA-1 hash code that has 40 hexadecimal digits but the
first five or six are usually unique and can be used as a shorthand (i.e.
easier to read and type) substitute for the whole hash code.
Greg has also indicated that one can see the history of the various commits
by running Git log...is this the best way to view these commits or is there a
GUI-based list that is accessible?
You can view the commit history of the project git repositories on Source
Forge just as you could before with Subversion. For example here is the current
commit history for the master branch on Source Forge for the WSJT-X project:
https://sourceforge.net/p/wsjt/wsjtx/commit_browser
Does the WSJT-X 1.9.2 build 308245 implement all of the commits shown in the
Git log run today?
It contains all the changes included in the commit [308245] which at the time
of writing is the HEAD of the master branch i.e. the latest of the published
development code.
Thanks!
Ed, K0KC
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
