On Sun, May 19, 2019 at 6:53 PM Martin Landa wrote:
> Hi,
>
> ne 19. 5. 2019 v 17:43 odesílatel Markus Metz
> Ideally, you would set up the local repo such that you pull from upstream
> and push to your fork.
>
> This is doable with: https://stackoverflow.com/a/4523625/592289
Nevertheless,
On Sun, May 19, 2019 at 5:53 PM Martin Landa wrote:
> ne 19. 5. 2019 v 17:43 odesílatel Markus Metz
> napsal:
> > For those who do have write access to upstream, it might be safer to have
> > origin refer to the personal fork. Ideally, you would set up the local repo
> > such that you pull
Hi,
ne 19. 5. 2019 v 17:43 odesílatel Markus Metz
napsal:
> For those who do have write access to upstream, it might be safer to have
> origin refer to the personal fork. Ideally, you would set up the local repo
> such that you pull from upstream and push to your fork.
+1 Ma
--
Martin
On Sun, May 19, 2019 at 5:24 PM Vaclav Petras wrote:
>
>
>
> On Sat, May 18, 2019 at 12:11 PM Markus Neteler wrote:
>>
>>
>> On Sat, May 18, 2019 at 5:59 PM Panagiotis Mavrogiorgos
>> wrote:
>> >
>> > I would suggest that:
>> >
>> > - even core devs fork the main repo
>> > - "origin" is the
On Sat, May 18, 2019 at 12:11 PM Markus Neteler wrote:
>
> On Sat, May 18, 2019 at 5:59 PM Panagiotis Mavrogiorgos
> wrote:
> >
> > I would suggest that:
> >
> > - even core devs fork the main repo
> > - "origin" is the personal remote GRASS repository (e.g. in my case
>
On Sat, 18 May 2019, 19:11 Markus Neteler, wrote:.
>
> For fetching the updates, is this enough:
>
> git pull --all
> ?
>
Μmm... sometimes yes, but I wouldn't suggest it.
Git pull is essentially 2 operations in one. It is a git fetch, followed by
a git merge.
The potential problem is with the
Hi Panos, all,
On Sat, May 18, 2019 at 5:59 PM Panagiotis Mavrogiorgos
wrote:
>
> hello Markus,
>
> I would suggest that:
>
> - even core devs fork the main repo
> - "origin" is the personal remote GRASS repository (e.g. in my case
> https://github.com/pmav99/grass)
> - everyone adds the main
hello Markus,
I would suggest that:
- even core devs fork the main repo
- "origin" is the personal remote GRASS repository (e.g. in my case
https://github.com/pmav99/grass)
- everyone adds the main GRASS repository as a secondary remote (e.g.
"upstream")
This way:
1. You always push to
Hi devs,
please stay tuned for re-enabled write access (for merging), we are
working on it.
We just have a lot on our plate here during the Berlin sprint (locals
and remote participants).
cheers,
Markus
___
grass-dev mailing list
Hi,
On Thu, May 16, 2019 at 3:16 PM Vaclav Petras wrote:
> +1 for Markus, Carmen, and Bas. That's what I see used elsewhere too.
Great, thanks for the suggestions.
I have written up a draft document:
https://trac.osgeo.org/grass/wiki/HowToGit
Please expand, discuss, ...
Markus
Hi Panos and all,
On Fri, May 17, 2019 at 5:09 AM Panagiotis Mavrogiorgos
wrote:
>
> I would argue that even core developers should not be using the main repo
> as their
> personal one and that, at least most of the time, they should instead be
> using the same
> procedure as every other
Dear all,
I would argue that even core developers should not be using the main repo
as their
personal one and that, at least most of the time, they should instead be
using the same
procedure as every other contributor.
Branches in git branches are really "cheap" (especially compared to e.g.
Martin Landa wrote
> čt 16. 5. 2019 v 8:25 odesílatel Helmut Kudrnovsky
> hellik@
> napsal:
>> https://trac.osgeo.org/grass/browser/grass-addons/tools/svn2git
>>
>> which file should be updated/checked?
>
> tools/svn2git/AUTHORS.txt
AUTHORS.txt updated in svn to primary gh email
-
On Thu, May 16, 2019 at 8:26 AM Bas Couwenberg wrote:
>
> On 2019-05-16 14:16, Markus Neteler wrote:
> > External contributors
> > # workflow for external contributors - they have to fork the repo in
> > GitHub Web interface
> > # create fork via github GUI
> > git clone $my_for_url
> > #
On 2019-05-16 14:16, Markus Neteler wrote:
External contributors
# workflow for external contributors - they have to fork the repo in
GitHub Web interface
# create fork via github GUI
git clone $my_for_url
# all steps see above
...
# push feature branch to own fork repo of GRASS GIS
git
On Thu, May 16, 2019 at 1:30 PM Vaclav Petras wrote:
>
>
>
> On Thu, May 16, 2019 at 2:07 AM Martin Landa wrote:
>>
>> Hi,
>>
>> st 15. 5. 2019 v 18:20 odesílatel Vaclav Petras
>> napsal:
>> > Another thing is the need for new contributing guidelines. Git is not
>> > Subversion and committing
On Thu, May 16, 2019 at 2:07 AM Martin Landa wrote:
> Hi,
>
> st 15. 5. 2019 v 18:20 odesílatel Vaclav Petras
> napsal:
> > 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
tly, I am struggling in another project with line endings which makes
contributions across plattforms complicated...
-Original Message-
From: grass-dev On Behalf Of Luca Delucchi
Sent: onsdag 15. mai 2019 22:21
To: Veronica Andreo
Cc: Martin Landa ; grass-dev
Subject: Re: [GRASS-dev] svn/tr
čt 16. 5. 2019 v 8:25 odesílatel Helmut Kudrnovsky napsal:
> https://trac.osgeo.org/grass/browser/grass-addons/tools/svn2git
>
> which file should be updated/checked?
tools/svn2git/AUTHORS.txt
Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
Martin Landa wrote
> Hi,
>
> st 15. 5. 2019 v 21:32 odesílatel Helmut Kudrnovsky
> hellik@
> napsal:
>> svn: hellik
>>
>> gh account: hellik
>> email:
> hkmyricaria@
>
> in the case you have write access to Addons, you can directly modify
> the file :-) Thanks, Ma
I have write access
Hi,
st 15. 5. 2019 v 21:32 odesílatel Helmut Kudrnovsky napsal:
> svn: hellik
>
> gh account: hellik
> email: hkmyrica...@gmail.com
in the case you have write access to Addons, you can directly modify
the file :-) Thanks, Ma
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
Hi,
st 15. 5. 2019 v 18:47 odesílatel Markus Neteler napsal:
> This are the authors who have a GitHub account known to us. There is a lookup
> table which maps SVN account to GitHub account (in addons/tools/svn2git
> somewhere).
Hi,
st 15. 5. 2019 v 18:20 odesílatel Vaclav Petras napsal:
> 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). What other OSGeo projects are doing is that
>
On Wed, May 15, 2019 at 4:24 PM Markus Neteler wrote:
>
> On Wed, May 15, 2019 at 10:20 PM Luca Delucchi
wrote:
> > On Wed, 15 May 2019 at 21:40, Veronica Andreo
wrote:
> > >> Another thing is the need for new contributing guidelines. Git is
not Subversion and committing to master won't work
Markus Neteler wrote
> On Wed, May 15, 2019 at 9:32 PM Helmut Kudrnovsky
> hellik@
> wrote:
>>
>> Markus Neteler wrote
>> > So, if someone isn't listed yet:
>> > Please get a GitHub account and/or communicate it to us (name + related
>> > email).
>>
>> svn: hellik
>>
>> gh account: hellik
>
>
On Wed, May 15, 2019 at 10:20 PM Luca Delucchi wrote:
> On Wed, 15 May 2019 at 21:40, Veronica Andreo wrote:
> >> 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
On Wed, 15 May 2019 at 21:40, Veronica Andreo 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
On Wed, May 15, 2019 at 9:32 PM Helmut Kudrnovsky wrote:
>
> Markus Neteler wrote
> > So, if someone isn't listed yet:
> > Please get a GitHub account and/or communicate it to us (name + related
> > email).
>
> svn: hellik
>
> gh account: hellik
You were already in the list.
But:
> email:
On Wed, May 15, 2019 at 9:27 PM Vaclav Petras wrote:
> On Wed, May 15, 2019 at 12:47 PM Markus Neteler wrote:
>> Later on, also commit claiming is possible and easy, so nothing is lost.
>
> Sounds good. I didn't know. We just have to be very clear about the current
> state not capturing
Hi,
El mié., 15 may. 2019 13:20, Vaclav Petras escribió:
>
>
> On Wed, May 15, 2019 at 9:14 AM Martin Landa
> wrote:
>
>> Hi,
>>
>> st 15. 5. 2019 v 9:51 odesílatel Martin Landa
>> napsal:
>> > Something strange happen with svn repo after r74441. I will publish
>> > testing repo for public
Markus Neteler wrote
> So, if someone isn't listed yet:
> Please get a GitHub account and/or communicate it to us (name + related
> email).
svn: hellik
gh account: hellik
email: hkmyrica...@gmail.com
-
best regards
Helmut
--
Sent from:
On Wed, May 15, 2019 at 12:47 PM Markus Neteler wrote:
>
> Later on, also commit claiming is possible and easy, so nothing is lost.
>
Sounds good. I didn't know. We just have to be very clear about the current
state not capturing everyone.
___
Hi,
a quick comment on this one:
Vaclav Petras schrieb am Mi., 15. Mai 2019, 18:20:
>
> ...
> I was also looking at the list of contributors [6]. I know this was
> discussed, but now I'm not really sure what to expect there.
>
> [6] https://github.com/grass-svn2git/grass/graphs/contributors
On Wed, May 15, 2019 at 9:14 AM Martin Landa wrote:
> Hi,
>
> st 15. 5. 2019 v 9:51 odesílatel Martin Landa
> napsal:
> > Something strange happen with svn repo after r74441. I will publish
> > testing repo for public review hopefully today.
>
> OK, finally a new fresh grass repo preview
> [2] https://github.com/grass-svn2git/grass
[2] https://github.com/grass-svn2git/grass/branches/all
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
Hi,
st 15. 5. 2019 v 9:51 odesílatel Martin Landa napsal:
> Something strange happen with svn repo after r74441. I will publish
> testing repo for public review hopefully today.
OK, finally a new fresh grass repo preview available for review (last
processed commit 74475).
Please compare git
Hi,
po 13. 5. 2019 v 15:32 odesílatel Martin Landa napsal:
> unfortunately attempt to run `git svn fetch` incrementally fails with
> similar error:
>
> $ git svn -r74443:75000 --authors-file=../AUTHORS.txt fetch
> Error from SVN, (160006): Invalid filesystem revision number: No such
> revision
po 13. 5. 2019 v 15:24 odesílatel Martin Landa napsal:
unfortunately attempt to run `git svn fetch` incrementally fails with
similar error:
$ git svn -r74443:75000 --authors-file=../AUTHORS.txt fetch
Error from SVN, (160006): Invalid filesystem revision number: No such
revision 74543
Ma
--
po 13. 5. 2019 v 15:01 odesílatel Martin Landa napsal:
r74440 = 1f1209cbe0074f1e6451b4ed40f56a22192724e7 (refs/remotes/origin/trunk)
Mraster/r.to.vect/areas_io.c
Mraster/r.to.vect/lines.c
Mraster/r.to.vect/lines_io.c
r74441 = 2fb78d92ee0ad2570a4388b30aeb3cdc63326cdb
Hi,
po 13. 5. 2019 v 14:58 odesílatel Martin Landa napsal:
> > https://trac.osgeo.org/grass/changeset/74542
> > Error: Invalid Changeset Number
> > NoSuchChangeset: No changeset 74542 in the repository
> >
> > ... but that number is nonsense, as it was not reached yet.
>
> yes, this error comes
Hi,
po 13. 5. 2019 v 14:11 odesílatel Markus Neteler napsal:
> > r74442 = a3741bbbdfc31118ea9ab9d98a6bd15a39b6fa83
> > (refs/remotes/origin/trunk)
> > Error from SVN, (160006): Invalid filesystem revision number: No such
> > revision 74542
>
> In fact, not there:
>
>
On Mon, May 13, 2019 at 1:31 PM Martin Landa wrote:
>
> Hi,
>
> po 13. 5. 2019 v 13:21 odesílatel Moritz Lennert
> napsal:
> > I think we just need to get the ball rolling. There will certainly be
> > some transition pain, but if we try to prepare everything to perfection
> > it will never
Hi,
po 13. 5. 2019 v 13:21 odesílatel Moritz Lennert
napsal:
> I think we just need to get the ball rolling. There will certainly be
> some transition pain, but if we try to prepare everything to perfection
> it will never happen ;-)
right, currently I am working on source code migration.
On 12/05/19 18:19, Markus Neteler wrote:
On Fri, May 10, 2019 at 5:06 PM Martin Landa wrote:
Hi,
út 7. 5. 2019 v 10:26 odesílatel Martin Landa napsal:
commits can be referenced to github issues. Issue migration needs to
be also done on private repository. This would require to set up empty
On Fri, May 10, 2019 at 5:06 PM Martin Landa wrote:
>
> Hi,
>
> út 7. 5. 2019 v 10:26 odesílatel Martin Landa napsal:
> > commits can be referenced to github issues. Issue migration needs to
> > be also done on private repository. This would require to set up empty
> > private repo, migrate
On Fri, May 10, 2019 at 4:03 PM Helmut Kudrnovsky wrote:
> Markus Neteler wrote
> > On Fri, May 10, 2019 at 1:12 PM Helmut Kudrnovsky
> >> so far I couldn't find a solution for the winGRASS trunk regression
> >
> > The only way I see is to revert the change and see if it works again.
> > If yes,
Hi,
út 7. 5. 2019 v 10:26 odesílatel Martin Landa napsal:
> commits can be referenced to github issues. Issue migration needs to
> be also done on private repository. This would require to set up empty
> private repo, migrate tickets and than transfer ticket using GitHub
> API to public repo.
Markus Neteler wrote
> On Fri, May 10, 2019 at 1:12 PM Helmut Kudrnovsky
> hellik@
> wrote:
> ...
>> so far I couldn't find a solution for the winGRASS trunk regression
>
> The only way I see is to revert the change and see if it works again.
> If yes, break this big commit into chunks and
On Fri, May 10, 2019 at 1:12 PM Helmut Kudrnovsky wrote:
...
> so far I couldn't find a solution for the winGRASS trunk regression
The only way I see is to revert the change and see if it works again.
If yes, break this big commit into chunks and try further.
Markus
Hi Vero,
>See Martin's original mail and links. The tickets that need to be >reviewed
are those with milestone 7.0.7 and 7.2.4, as to know if >they are still
valid and milestone should be moved to 7.6.2
IMHO when I go through the tickets for 7.0.7 and 7.2.4, an additional check
with trunk
Hi Helli
El jue., 9 may. 2019 19:53, Helmut Kudrnovsky escribió:
> Veronica Andreo wrote
> > Hola :)
> >
> > El mar., 7 may. 2019 a las 16:20, Veronica Andreo (
>
> > veroandreo@
>
> > )
> > escribió:
> >
> >> El mar., 7 may. 2019 a las 11:54, Martin Landa (
>
> > landa.martin@
>
> > )
> >>
Veronica Andreo wrote
> Hola :)
>
> El mar., 7 may. 2019 a las 16:20, Veronica Andreo (
> veroandreo@
> )
> escribió:
>
>> El mar., 7 may. 2019 a las 11:54, Martin Landa (
> landa.martin@
> )
>> escribió:
>>
>>> Hi,
>>>
>>> út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo
> veroandreo@
>
Hola :)
El mar., 7 may. 2019 a las 16:20, Veronica Andreo ()
escribió:
> El mar., 7 may. 2019 a las 11:54, Martin Landa ()
> escribió:
>
>> Hi,
>>
>> út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo
>> napsal:
>> > I'd suggest then to set a deadline for ticket review by reporters, eg:
>> this
El mar., 7 may. 2019 a las 11:54, Martin Landa ()
escribió:
> Hi,
>
> út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo
> napsal:
> > I'd suggest then to set a deadline for ticket review by reporters, eg:
> this Sunday (or any other date before the planned code sprint in Berlin)
>
> could work.
Hi,
út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo napsal:
> I'd suggest then to set a deadline for ticket review by reporters, eg: this
> Sunday (or any other date before the planned code sprint in Berlin)
could work. Till Sunday I will have also time to test issue migration
a bit more.
Hi Martin,
Thanks for explanation and for all your hard work! :)
El mar., 7 may. 2019 05:28, Martin Landa escribió:
> Hi,
>
> po 6. 5. 2019 v 23:06 odesílatel Veronica Andreo
> napsal:
> > Say, if source code migration starts tomorrow, how long it would take?
> Then set that day (+2 or 3 if
Hi,
po 6. 5. 2019 v 23:06 odesílatel Veronica Andreo napsal:
> Say, if source code migration starts tomorrow, how long it would take? Then
> set that day (+2 or 3 if you want) as deadline for tickets revision, then
> migrate tickets, done :)
source code migration will take a few hours. See my
Hi,
po 6. 5. 2019 v 22:49 odesílatel Markus Neteler napsal:
> Why wait for that with the source code migration?
> Please let's start with it. The tickets can follow in a second step.
> This also prevents us from being overloaded.
my idea to do migration in one step comes from assumption that
Hi,
El lun., 6 may. 2019 17:49, Markus Neteler escribió:
> Hi Martin,
>
> On Mon, May 6, 2019 at 11:41 AM Martin Landa
> wrote:
> >
> > Dear all,
> >
> > based on decision made by PSC [1], the GRASS GIS source code will be
> > moved from SVN hosted by OSGeo to Git hosted by GitHub.com. More
>
Hi Martin,
On Mon, May 6, 2019 at 11:41 AM Martin Landa wrote:
>
> Dear all,
>
> based on decision made by PSC [1], the GRASS GIS source code will be
> moved from SVN hosted by OSGeo to Git hosted by GitHub.com. More
> details at [2].
[...migration of tickets ...]
> When this part will be done
Hi,
po 6. 5. 2019 v 12:10 odesílatel Helmut Kudrnovsky napsal:
> > In this regard I would like to ask you for ASSISTANCE. All
> >tickets with milestone 7.0 [3], 7.2 [4] should be reviewed and either
> >to be closed or milestone changed to 7.4 (or 7.6/7.8/8.0).
>
> do we have some date until when
hi Martin,
> In this regard I would like to ask you for ASSISTANCE. All
>tickets with milestone 7.0 [3], 7.2 [4] should be reviewed and either
>to be closed or milestone changed to 7.4 (or 7.6/7.8/8.0).
do we have some date until when tickets should be reviewed?
-
best regards
Helmut
--
Dear all,
based on decision made by PSC [1], the GRASS GIS source code will be
moved from SVN hosted by OSGeo to Git hosted by GitHub.com. More
details at [2].
It's also planned to move open issues from trac to GitHub issue
system. In this regard I would like to ask you for ASSISTANCE. All
63 matches
Mail list logo
