> -----Original Message----- > From: Jody Garnett [mailto:jody.garn...@gmail.com] > Sent: 25 August 2015 21:07 > To: Geoserver-devel <geoserver-devel@lists.sourceforge.net> > Subject: [Geoserver-devel] PSC Meeting Minuets, August 25th 2015 > > GeoTools / GeoServer Meeting 2015-08-25 > =================================
> The real question is which pull requests are going to make the cut. > Is https://github.com/geoserver/geoserver/pull/1191 - "Add option to disable INSPIRE capabilities" on the list for consideration? I'd like to add another one to address https://osgeo-org.atlassian.net/browse/GEOS-6435 - "Add INSPIRE extended capabilities section to WCS GetCapabilities response" but my code for that builds on top of 1191 so I can't really submit it as a pull request until/if 1191 is merged I guess. A related general question... When master goes ahead of the commit on which a pull request I submitted was based, is it best practice for me to rebase the pull request branch on top of the latest master and checking the build whenever I notice commits to master? Marcus Sen British Geological Survey Keyworth Nottingham NG12 5GG Web: http://www.bgs.ac.uk ________________________________ This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system. ________________________________ ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
