Yeah..forget the rev#...but the date?
Git branch/merging retains the date/time of the commits both directions. In
your scenario both would show the same date/time and the same git hash #. But
another update (on another day) would clearly show one more current
(i.e..master).
Or are you referri
Mike and all,
On 7/10/2018 8:43 AM, Black Michael via wsjt-devel wrote:
One other idea that is more git-centric...how about we use date + 6
digit for the About revision? This would also help solve those who
think RCn is more current than the general release.
git log --date-format=:%Y%m%d
Mar
I'll try to carve out some time this summer to work on a means to
automatically check for the latest program version on the wsjt-x
website. I talked about it last fall, but got really busy. I'm really
not any less busy now, but it's time to get that 'feature' going.
-Brian N9ADG
On Tue, Jul 10,
I'm not deriding git at all. The rev# is a common question in git.
One other idea that is more git-centric...how about we use date + 6 digit for
the About revision? This would also help solve those who think RCn is more
current than the general release.
git log --date-format=:%Y%m%dMarry that
On 07/10/2018 11:05 AM, Bill Somerville wrote:
> the only difference should be that you clone the git repository rather
> than checkout the old Subversion one. As with Subversion the git
> repository web page on SourceForge
> (https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/) has a
> pre-const
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
k0kc@arrl.nethttp://k0kc.us/
On Monday, July 9, 2018, 7:24:25 PM EDT,
On 10/07/2018 07:35, Claude Frantz wrote:
Please give us your recommendation about how to switch from svn to git,
in the current context.
Best wishes,
Claude (DJ0OT)
Hi Claude,
the only difference should be that you clone the git repository rather
than checkout the old Subversion one. As wit
On 10/07/2018 04:49, Black Michael via wsjt-devel wrote:
We will be seeing more of this same question in the future I'm sure so
some consideration should be given to making it a one-up counter again
perhaps appending it to the 6-digit git number.
Mike,
we have seen the same question with svn
Hi Bill,
Downloaded tag 1.9.1 from new git layout to my iMac; build completes without a
problem; after launch: About WSJT-X shows: WSJT-X v1.9.2-devel 308245.
The new system works well.
— John G4KLA
--
Check out the
e.fra...@bayern-mail.de]
Sent: Tuesday, July 10, 2018 12:35 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Building WSJT-X Developmental Software
Hi Bill & All,
Please give us your recommendation about how to switch from svn to git, in
the current context.
Best wi
Hi Bill & All,
Please give us your recommendation about how to switch from svn to git,
in the current context.
Best wishes,
Claude (DJ0OT)
--
Check out the vibrant tech community on one of the world's most
engaging tech
: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] Building WSJT-X Developmental Software
I was speaking from a human/user perspective as I'm aware what a hash
is...although collisions in git can occur (unlikely) which never occur in a
one-up counting system (ba
I was speaking from a human/user perspective as I'm aware what a hash
is...although collisions in git can occur (unlikely) which never occur in a
one-up counting system (barring rollover).
If one were to say "XX" is the most current version of WSJT-X the vast
majority of users would not kno
Hi Mike,
some comments in line below.
On 09/07/2018 17:51, Black Michael via wsjt-devel wrote:
No...that number does not increment...it's basically random with git
(it's a hash value). It's just the first 6 digits of the "commit"
line which is a hexadecimal number
The git SHA-1 hash codes are
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 bu
No...that number does not increment...it's basically random with git (it's a
hash value). It's just the first 6 digits of the "commit" line which is a
hexadecimal number
There is a means to making an increment version # but it's not frequently used
-- basically one way is to count the # of log
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 bu
17 matches
Mail list logo
