[GRASS-dev] svn/trac -> git/github migration plan
Luca Delucchi
lucadeluge at gmail.com
Wed May 15 13:20:38 PDT 2019
On Wed, 15 May 2019 at 21:40, Veronica Andreo <veroandreo at gmail.com> wrote:
>
> Hi,
>
Hi,
>> Another thing is the need for new contributing guidelines. Git is not Subversion and committing to master won't work (please, let me know if you want me to show some examples).
>
>
> I am very interested in such examples, esp. how the workflow will be from now on for example when making a small change in manuals.
>
Yes, it is important to know this. How to use branches and also how to
update local version from the master one. Should we use a private
clone and make pull request to the main repository o use the main
repository directly?
> I think it is very important that those of you more familiar with git and GitHub develop or show example workflows of how to contribute, backport (if that will be still called like that), and so on.
>
+1
> my 0.01 cent
> Vero
>
--
ciao
Luca
www.lucadelu.org
More information about the grass-dev
mailing list