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, 2018 at 5:43 AM, Black Michael via wsjt-devel
<[email protected]> wrote:
> 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%d
> Marry that with the current revision#.
>
> So we'd end up with a human friendly 20180702/308245
>
> de Mike W9MDB
>
>
>
>
> On Tuesday, July 10, 2018, 3:36:19 AM CDT, Bill Somerville
> <[email protected]> wrote:
>
>
> 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 revision numbers but you still
> ignore that svn has the same issue because it supports branching but
> revision numbers are not incremented separately for each branch. Here's a
> simple example:
>
> trunk e.g. v2.0.0 gets a change, let's say revision number r1000. A fix is
> applied to an old branch e.g. 1.0.1 for fix an urgent defect only in that
> old branch, let's say that is revision r1001. So you are saying that
> revision numbers allow a user to determine the latest version. So who has
> the latest version, is it r1001 which is version1.0.1 or is it r1000 which
> is version 2.0.0?
>
> This should make it perfectly clear that svn revision numbers tell us
> nothing about the logical linage of a code line. Stop deriding git as a
> version control system using invalid arguments please.
>
>
> 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
>

------------------------------------------------------------------------------
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

Reply via email to