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 referring to cross-repository patches?...then all bets are off...or
doing manual diff/patch.
As long as we are using git branching it would appear to be a valid approach.
Can't say I've ever used this approach so would like to know any weaknesses for
future reference.
Mike
On Tuesday, July 10, 2018, 9:16:38 AM CDT, Joe Taylor <[email protected]>
wrote:
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
> Marry that with the current revision#.
>
> So we'd end up with a human friendly 20180702/308245
Surely you can see that this has the same problem that Bill brought to
your attention a few minutes ago:
On 7/10/2018 4:33 AM, Bill Somerville wrote:
> 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?
Your suggested approach would tag v1.0.1 with a later date than v2.0.0,
because the change to v1.0.1 was made after the latest one to v2.0.0.
This might be even more confusing.
Perhaps it's time for a more general policy statement about using our
source code and the differences between development code and released
code. You may expect a message on this topic a short time after this one.
-- 73, Joe, K1JT
------------------------------------------------------------------------------
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
