Hi Panos,
thanks so much for writing up this guide which looks very good to me
(and saves disk space; and offers an approach more close to those
freshly coming from SVN)!
Some comments + questions inline:
On Mon, May 20, 2019 at 10:23 AM Panagiotis Mavrogiorgos
wrote:
>
> Hello Markus
>
> I
Hello Markus
I don't have real-world experience with this, but I am not sure if changing
branches and
distcleaning/recompiling is the most convenient workflow. I think I would
prefer to have
multiple local repositories with different branches checked out. Thankfully
git makes it
rather easy to
rass-dev-requ...@lists.osgeo.org<mailto:grass-dev-requ...@lists.osgeo.org>
wrote:
Message: 2
Date: Sun, 19 May 2019 19:27:34 +0200
From: Markus Neteler mailto:nete...@osgeo.org>>
To: GRASS developers list
mailto:grass-dev@lists.osgeo.org>>
Subject: [GRASS-dev] git: how to switch
rg>>
Subject: [GRASS-dev] git: how to switch between branches?
Message-ID:
mailto:calfmhhvwdzhoqu07q8s12qn10qmmgqdavvydpjcrktyxzhc...@mail.gmail.com>>
Content-Type: text/plain; charset="UTF-8"
Hi,
being a kind of git newbie, I'm struggly with switching between the
differen
Hi,
being a kind of git newbie, I'm struggly with switching between the
different release branches (and master).
Starting from a clean state (nothing downloaded yet), it this correct:
## 0. getting the code: fork in GH, then
# git clone g...@github.com:your_GH_account/grass.git
# git remote ...
