Sorry. It had a backporting label and I thought there was an auto-backport 
running...

But I can backport this one tonight. Good to learn how to backport anyway (it 
is well documented on the wiki).

Cheers
Stefan
________________________________
Fra: Markus Neteler <nete...@osgeo.org>
Sendt: lørdag 16. november 2019 11:51
Til: Stefan Blumentrath <stefan.blumentr...@nina.no>
Kopi: GRASS developers list <grass-dev@lists.osgeo.org>
Emne: Re: [OSGeo/grass] r.in.wms: write string not bytes to capabilities file 
(#195)

Hi Stefan,

On Fri, Nov 15, 2019 at 7:56 PM Stefan Blumentrath 
<notificati...@github.com<mailto:notificati...@github.com>> wrote:

Merged #195<https://github.com/OSGeo/grass/pull/195> into master.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on 
GitHub<https://github.com/OSGeo/grass/pull/195?email_source=notifications&email_token=AAJ4GRFUUH4CGP42UYK65YDQT3WG7A5CNFSM4JN2H422YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOU4OFK7Q#event-2803651966>,
 or 
unsubscribe<https://github.com/notifications/unsubscribe-auth/AAJ4GRG5IJRFEU7U6YKJ22LQT3WG7ANCNFSM4JN2H42Q>.

...was this not backported on purpose?

I would invite all devs to:
- either backport themselves,
- or clearly indicate: do not backport,
- or state: pls someone backport it (seems to be mostly me but that's ok), 
there is a PR label for that.

We missed in 7.8.1 an important backport exactly due to this unclear situation.

I am not keen on manually compare every PR to see if it was backported or not...

thanks,
Markus

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to