It's been a while since I pulled the most recent changes from the 7.5
trunk so when I tried to do so just now ("svn up") grass responded that my
local copy is "At revision 72718". Is this really the current revision?
TIA,
Rich
It's been a while since I pulled the most recent changes from the 7.5
trunk so when I tried to do so just now ("svn up") grass responded that my
local copy is "At revision 72718". Is this really the current revision?
TIA,
Rich
Rich Shepard wrote
It's been a while since I pulled the most recent changes from the 7.5
trunk so when I tried to do so just now ("svn up") grass responded that my
local copy is "At revision 72718". Is this really the current revision?TIA,
Rich
_______________________________________________
grass-user mailing list
grass-user@.osgeo
an easy information point about revisions is the commit ML list, e.g.
https://lists.osgeo.org/pipermail/grass-commit/2018-May/date.html
-----
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
On Sat, 19 May 2018, Helmut Kudrnovsky wrote:
local copy is "At revision 72718". Is this really the current revision?
an easy information point about revisions is the commit ML list, e.g.
https://lists.osgeo.org/pipermail/grass-commit/2018-May/date.html
Helmut,
That'a really useful. Thanks.
The last entry on that page is 72721. But, when I try to upgrade using
subversion I'm now told that my directory is at that revision number while
nothing is downloaded.
What might be going on here?
Best regards,
Rich
On Sat, 19 May 2018, Rich Shepard wrote:
The last entry on that page is 72721. But, when I try to upgrade using
subversion I'm now told that my directory is at that revision number while
nothing is downloaded.
I am checking out the repository. That will be the latest. Why upgrading
failed -- twice -- I've no idea.
Rich