#3471: Custom dropdown control doesn’t recognize mouse events
--+
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: reopened
Priority: major| Milestone: 7.6.2
Component: wxGUI
Hi,
so 18. 5. 2019 v 22:46 odesílatel Paulo van Breugel
napsal:
> If add-ons are made available from personal repositories, will there still be
> a central page with links to all manual pages
> (https://grass.osgeo.org/grass76/manuals/addons/)? I always find this a very
> convenient place to c
Hi,
so 18. 5. 2019 v 17:00 odesílatel Martin Landa napsal:
> * tools/ content could be moved to a new git repo,
> `grass-maintenance-tools` (any idea for better name).
if no objections I would suggest to create a new repo under OSGeo
organization in next hours/days.
Ma
--
Martin Landa
http://
Hi,
ne 19. 5. 2019 v 11:52 odesílatel Martin Landa napsal:
> > * tools/ content could be moved to a new git repo,
> > `grass-maintenance-tools` (any idea for better name).
another option is to keep tools in `grass-addons` repo, just to move
them into separated branch. In summary, list of branche
Dear Martin and all,
is there anything add-ons authors should do from their side?
Thanks for all of the hard work, Nikos
* Martin Landa [2019-05-19 11:06:35 +0200]:
Hi,
so 18. 5. 2019 v 22:46 odesílatel Paulo van Breugel
napsal:
If add-ons are made available from personal repositories, wi
On Sun, May 19, 2019 at 8:50 AM Martin Landa wrote:
> Hi,
>
> ne 19. 5. 2019 v 11:52 odesílatel Martin Landa
> napsal:
> > > * tools/ content could be moved to a new git repo,
> > > `grass-maintenance-tools` (any idea for better name).
>
> another option is to keep tools in `grass-addons` repo,
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
> https://github.com/pmav9
#3844: Make Region importable from pygrass.gis
--+-
Reporter: pmav99 | Owner: grass-dev@…
Type: enhancement | Status: closed
Priority: normal | Milestone: 7.8.0
Component: PyGRASS |Version: svn-trunk
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 pers
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 Landa
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 fro
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, occas
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 ...
Hi,
so 18. 5. 2019 v 19:48 odesílatel Martin Landa napsal:
> but unfortunately git appeared to be broken in my msys2 installation
> (calling `git` command had no effect). So I am trying to reinstall
> msys2 from scratch.
it helped partially. git clone is working in msys64 64bit. But fails
in msy
#3722: migrate grass svn repositories to git
--+-
Reporter: martinl | Owner: grass-dev@…
Type: task | Status: closed
Priority: major| Milestone:
Component: Default |Version: unspecified
On Sun, May 19, 2019 at 2:03 PM Martin Landa wrote:
>
> This opens long time planned question. Do we really need to provide
> WinGRASS 32bit builds. Only 64bit builds would enough probably. Any
> opinion? Ma
Do we have download statistics for 32bit installers?
Martin Landa wrote
> Hi,
>
> so 18. 5. 2019 v 19:48 odesílatel Martin Landa <
> landa.martin@
> > napsal:
>> but unfortunately git appeared to be broken in my msys2 installation
>> (calling `git` command had no effect). So I am trying to reinstall
>> msys2 from scratch.
>
> it helped partially.
#3849: Do we need to clear the screen when entering/exiting GRASS?
-+-
Reporter: pmav99 | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Startup |Version: svn-t
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
Currently Senior Research Fellow, Institute for Advance
#3849: Do we need to clear the screen when entering/exiting GRASS?
--+-
Reporter: pmav99 | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Startup |Version:
Markus and others,
I've looked at this a little now, and here is a possible workflow. For Git
sophisticates, I realize that this negates to some extent the lightweight
flexibility of the Git approach to versioning. And of course, not everyone has
to do this. But to create separate source distri
21 matches
Mail list logo
