[GRASS-dev] instructions to update my local copy of trunk

Markus Metz markus.metz.giswork at gmail.com
Sun Jun 2 23:49:41 PDT 2019

On Sun, Jun 2, 2019 at 11:12 PM Markus Neteler <neteler at osgeo.org> wrote:
> On Sun, Jun 2, 2019 at 10:52 PM Panagiotis Mavrogiorgos
> <pmav99 at gmail.com> wrote:
> ...
> > Markus wrote:
> >> It there a way (magic flag?) to avoid this out-of-sync in the first
> >> E.g., for the cronjobs I do not want to go there weekly and "git push"
> >> stuff around.
> >
> > Yes, but we need to know the contents of the cron scripts first.
> It simply follows the HowToGit on trac which leads to the mentioned
> What I am searching for is that the disk copy is the same as on the
> server.

Which version on the server? The orginal GRASS repo (
https://github.com/OSGeo/grass.git) or a fork? If the aim is to have an
unmodified local copy that is in sync with the original GRASS repo, you
don't need any other remote and it should be enough to pull.

> As it is a cronjob there will be no local changes. Still, some
> push magic seems to me missing from
> https://trac.osgeo.org/grass/wiki/HowToGit#Keepyourlocalsourcecodeuptodate

In this case (have a local copy in sync with
https://github.com/OSGeo/grass.git) push is not needed (no modifications
and no fork added as another remote).

Works ar t least for me.

Markus M
> thanks,
> Markus
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190603/2a67e2d8/attachment.html>

More information about the grass-dev mailing list