Index: ndors/.gitignore
===================================================================
--- /vendors/.gitignore	(revision 10669)
+++ 	(revision )
@@ -1,2 +1,0 @@
-*.swp
-etc/fcm/*.cfg
Index: ndors/.mailmap
===================================================================
--- /vendors/.mailmap	(revision 10669)
+++ 	(revision )
@@ -1,11 +1,0 @@
-Ben Fitzpatrick      <ben.fitzpatrick@metoffice.gov.uk>   benfitzpatrick      <ben.fitzpatrick@metoffice.gov.uk>
-David Matthews       <david.matthews@metoffice.gov.uk>    dpmatthews          <david.matthews@metoffice.gov.uk>
-Matt Pryor           <matt.pryor@metoffice.gov.uk>        Matt Pryor          <mkjpryor@gmail.com>
-Matt Pryor           <matt.pryor@metoffice.gov.uk>        mkjpryor            <mkjpryor@gmail.com>
-Matt Shin            <matthew.shin@metoffice.gov.uk>      matthew.shin        <matthew.shin@metoffice.gov.uk>
-Matt Shin            <matthew.shin@metoffice.gov.uk>      matthewrmshin       <matthew.shin@metoffice.gov.uk>
-Matt Shin            <matthew.shin@metoffice.gov.uk>      matthewrmshin       <matthewrmshin@yahoo.co.uk>
-Roddy Sharp          <roddy.sharp@metoffice.gov.uk>       r-sharp             <r-sharp@users.noreply.github.com>
-Stuart Whitehouse    <stuart.whitehouse@metoffice.gov.uk> scwhitehouse        <stuart.whitehouse@metoffice.gov.uk>
-Martin Dix           <martin.dix@csiro.au>                MartinDix           <martin.dix@csiro.au>
-Kerry Day            <kerry.day@metoffice.gov.uk>         Kerry Day           <kaday@users.noreply.github.com>
Index: ndors/.travis.yml
===================================================================
--- /vendors/.travis.yml	(revision 10669)
+++ 	(revision )
@@ -1,27 +1,0 @@
-# Configuration for running FCM test battery on Travis CI
-# See https://travis-ci.org/ for more info.
-
----
-language: perl
-
-before_install:
-    - cat >"${HOME}/.bashrc" <<<"export PATH=${PWD}/bin:\$PATH"
-    - source "${HOME}/.bashrc"
-
-install: 
-    - sudo apt-get install -y build-essential gfortran
-    - sudo apt-get install -y libxml-parser-perl libconfig-inifiles-perl
-    - sudo apt-get install -y libdbi-perl libdbd-sqlite3-perl
-    # For some reason XML::Parser needs to be installed this way
-    - cpanm 'Config::IniFiles' 'XML::Parser'
-    # Latest Subversion
-    - sudo sh -c 'echo "deb http://opensource.wandisco.com/ubuntu `lsb_release -cs` svn19" >> /etc/apt/sources.list.d/subversion19.list'
-    - sudo wget -q http://opensource.wandisco.com/wandisco-debian.gpg -O- | sudo apt-key add -
-    - sudo apt-get update
-    - sudo apt-get install -y subversion libsvn-perl python-subversion
-    - sudo apt-get install -y heirloom-mailx
-    - sudo apt-get install -y python-pip
-    - sudo pip install trac
-
-script: 
-    - fcm test-battery -j 5
Index: ndors/ACKNOWLEDGEMENT.md
===================================================================
--- /vendors/ACKNOWLEDGEMENT.md	(revision 10669)
+++ 	(revision )
@@ -1,19 +1,0 @@
-# Acknowledgement for non-FCM Work
-
-Licences for non-FCM works included in this distribution can be
-found in the licences/ directory.
-
-Non-FCM works included in this distribution are listed below:
-
-doc/etc/bootstrap/:
-* Unmodified external software library copyright 2011-2015 Twitter, Inc
-  released under the MIT license.
-  See [Bootstrap](http://getbootstrap.com/).
-
-svn-hooks/svnperms.py:
-* Subversion repository pre-commit path-based permission checking utility,
-  written by [Gustavo Niemeyer](mailto:gustavo@niemeyer.net) and released under
-  Apache 2.0 license.
-  Original source downloaded from r1295006 at:
-  https://svn.apache.org/viewvc/subversion/trunk/tools/hook-scripts/svnperms.py
-  This version is modified to allow custom permission message per repository.
Index: ndors/CHANGES.md
===================================================================
--- /vendors/CHANGES.md	(revision 10669)
+++ 	(revision )
@@ -1,723 +1,0 @@
-# FCM Changes
-
-Go to https://github.com/metomi/fcm/milestones?state=closed
-for a full listing of issues for each release.
-
---------------------------------------------------------------------------------
-
-## 2017.10.0 (2017-10-03)
-
-FCM release 40.
-
-### Noteworthy Changes
-
-[#247](https://github.com/metomi/fcm/pull/247):
-fcm make: build: partially revert [#245](https://github.com/metomi/fcm/pull/245)
-so the link task will, as before, create a temporary dependent object library
-before linking the main object to it. However, users can now specify the
-`build.prop{link-without-ar}` setting in the configuration to prevent it from
-creating the temporary dependent object library, and put the full list of
-dependent object files in the linker command line instead.
-
---------------------------------------------------------------------------------
-
-## 2017.09.0 (2017-09-27)
-
-FCM release 39.
-
-### Noteworthy Changes
-
-[#246](https://github.com/metomi/fcm/pull/246):
-fcm make: new `description` setting to allow users to specify any string to
-describe the current make.
-
-[#245](https://github.com/metomi/fcm/pull/245):
-fcm make: build: a link task for creating an executable will no longer create
-an archive library with the `ar` command before calling the linker. The linker
-command will contain the full list of object files instead.
-
---------------------------------------------------------------------------------
-
-## 2017.02.0 (2017-02-24)
-
-FCM release 38.
-
-### Noteworthy Changes
-
-[#243](https://github.com/metomi/fcm/pull/243):
-fcm switch: fix Perl warning. This happened on an unexpected usage. A user has
-checked out an entire project tree, and then run `fcm switch trunk` on it.
-Clearly it did not work, but the added Perl warning was not helpful either.
-
---------------------------------------------------------------------------------
-
-## 2016.12.0 (2016-12-06)
-
-FCM release 37.
-
-### Noteworthy Changes
-
-[#241](https://github.com/metomi/fcm/pull/241):
-fcm branch-delete: fix Perl warning on branches in a Rosie repository.
-
-[#240](https://github.com/metomi/fcm/pull/240):
-fcm make: fix implementation of `build.prop{ignore-missing-dep-ns}`.
-
---------------------------------------------------------------------------------
-
-## 2016.10.0 (2016-10-07)
-
-FCM release 36.
-
-### Noteworthy Changes
-
-[#239](https://github.com/metomi/fcm/pull/239):
-fcm conflicts: handle tree conflict:
-*local file edit, incoming file replace upon merge*.
-
-[#238](https://github.com/metomi/fcm/pull/238):
-fcm make: use `TMPDIR` (if defined in the environment) for temporary files on
-load/dump of `ctx.gz`, instead of `/tmp/`.
-
---------------------------------------------------------------------------------
-
-## 2016.09.0 (2016-09-19)
-
-FCM release 35. Minor bug fix, and minor update to admin utilities.
-
-### Noteworthy Changes
-
-[#235](https://github.com/metomi/fcm/pull/235):
-fcm make: build: fix `sprintf` redundant argument warning on Perl 5.22+.
-
---------------------------------------------------------------------------------
-
-## 2016.05.1 (2016-05-19)
-
-FCM release 34. Minor update to admin utilities, nothing noteworthy for users.
-
---------------------------------------------------------------------------------
-
-## 2016.05.0 (2016-05-05)
-
-FCM release 33. Minor bug fix and update.
-
-### Noteworthy Changes
-
-[#229](https://github.com/metomi/fcm/pull/229):
-fcm commit, branch-create, branch-delete, etc: the default graphical editor for
-commit message is modified from `gedit` to `gvim -f`, as `gedit` is not
-reliable for running in the foreground.
-
-[#227](https://github.com/metomi/fcm/pull/227):
-fcm make: on gunzip of the context file, pass a file handle rather than a path
-to the `gunzip` function to work around problems when files are made read-only
-via ACL.
-
---------------------------------------------------------------------------------
-
-## 2016.02.0 (2016-02-11)
-
-FCM release 32. Minor bug fix and update.
-
-### Noteworthy Changes
-
-[#222](https://github.com/metomi/fcm/pull/222):
-Configuration file: fix variable substitution of value 0. A (environment)
-variable value of `0` was previously lost on substitution. This fixes the
-problem.
-
-[#219](https://github.com/metomi/fcm/pull/219):
-fcm make: extract: fix target status on conflict. On conflict, the target
-status was recorded incorrectly as unchanged. This caused incremental extracts
-to succeed in error. This change fixes the problem.
-
-[#215](https://github.com/metomi/fcm/pull/215):
-Improvements to version related functionality:
-* fcm version: now displays FCM_HOME location.
-* fcm make: new `require-version=MIN-VERSION [MAX-VERSION]` declaration.
-  If this declaration is specified and the current version is below
-  `MIN-VERSION` or if a `MAX-VERSION` is specified and the current version is
-  above it, the command will fail immediately.
-
---------------------------------------------------------------------------------
-
-## 2015.12.0 (2015-12-09)
-
-FCM release 31. Minor update.
-
-### Noteworthy Changes
-
-[#214](https://github.com/metomi/fcm/pull/214):
-fcm make: `build.prop` declarations: modifiers such as `dep.include`, `dep.o`,
-`no-dep.include` and `no-dep.o` are now supported with namespaces that are
-target names.
-
---------------------------------------------------------------------------------
-
-## 2015.11.0 (2015-11-17)
-
-FCM release 30. Minor update.
-
-### Noteworthy Changes
-
-[#208](https://github.com/metomi/fcm/pull/208):
-fcm make: build: now recognises more patterns as indicators of the existence of
-a main program in a C source file.
-
-[#207](https://github.com/metomi/rose/pull/207):
-fcm test-battery: now runs correctly in the absence of site/user configuration
-on recent Ubuntu distros.
-
---------------------------------------------------------------------------------
-
-## 2015.10.0 (2015-10-15)
-
-FCM release 29. Minor update.
-
-### Noteworthy Changes
-
-[#205](https://github.com/metomi/fcm/pull/205):
-fcm make: build: new setting `build.prop{checksum-method}=md5|sha1|...` allows
-users to choose MD5 or one of SHA algorithms in Perls' `Digest::SHA` to
-calculate the checksums of source and target files.
-
-[#204](https://github.com/metomi/fcm/pull/204):
-fcm branch-create: allow `--bob` as a synonym of `--branch-of-branch`.
-
---------------------------------------------------------------------------------
-
-## 2015.09.0 (2015-09-28)
-
-FCM release 28. Minor update to admin utilities, nothing noteworthy for users.
-
---------------------------------------------------------------------------------
-
-## 2015.08.0 (2015-08-19)
-
-FCM release 27. Minor update to admin utilities, nothing noteworthy for users.
-
---------------------------------------------------------------------------------
-
-## 2015.07.0 (2015-07-09)
-
-FCM release 26.
-
-### Noteworthy Changes
-
-[#197](https://github.com/metomi/fcm/pull/197):
-fcm make: build: fix target select modifier.
-* The `category` modifier should now work.
-* The `ns` modifier never worked, and is removed.
-  Instead `task` and `category` selection can now be filtered by name-space.
-
-[#196](https://github.com/metomi/fcm/pull/196):
-pre/post commit: improve changeset size diagnostic
-* pre-commit: log (but don't email) >1MB transactions
-* post-commit: report pre-commit size threshold (normally 10MB) for any >1MB
-  changesets
-
-[#192](https://github.com/metomi/fcm/pull/192):
-Primary location keyword: trailing slashes in values of primary location
-keywords will now removed automatically.
-
-[#191](https://github.com/metomi/fcm/pull/191):
-fcm (branch-)diff --graphical: will now use the option
-`--config-option config:working-copy:exclusive-locking-clients=` to prevent the
-client from being locked.
-
---------------------------------------------------------------------------------
-
-## 2015.05.0 (2015-05-28)
-
-FCM release 25.
-
-### Highlighted Changes
-
-[#188](https://github.com/metomi/fcm/pull/188):
-fcm make: allow multiple runs in same directory. A make can now be named, so
-multiple non-overlapping makes can work in the same directory. It is worth
-noting that once you have used this version of `fcm make` on a directory, older
-version of FCM will no longer work in incremental mode on the same directory.
-See also [metomi/rose#1604](https://github.com/metomi/rose/pull/1604).
-
-### Noteworthy Changes
-
-[#190](https://github.com/metomi/fcm/pull/190):
-fcm make: new `--archive` option. If archive mode is specified, TAR-GZIP these
-items by default:
-* `.fcm-make/cache/extract/`
-* `build/include/`
-* `build/o/`
-
-where `extract` and `build` are names of extract and build steps.
-Users can configure what to TAR-GZIP under `build/`.
-
-[#189](https://github.com/metomi/fcm/pull/189):
-fcm make: correctly support relocation of a make.
-
---------------------------------------------------------------------------------
-
-## 2015.03.0 (2015-03-26)
-
-FCM release 24.
-
-### Noteworthy Changes
-
-[#183](https://github.com/metomi/fcm/pull/183):
-Use of Subversion 1.6 with FCM is no longer recommended.
-
-[#181](https://github.com/metomi/fcm/pull/181):
-fcm make: source file find: ignore hidden paths only if paths are under
-the source root directory, i.e. it is now OK for the source root directory to
-be a hidden path itself.
-
-[#178](https://github.com/metomi/fcm/pull/178):
-fcm make: `.fcm-make/log` symbolic links are now relative. This should make it
-easier to relocate a build.
-
---------------------------------------------------------------------------------
-
-## 2015.02.0 (2015-02-10)
-
-FCM release 23.
-
-### Noteworthy Changes
-
-[#176](https://github.com/metomi/fcm/pull/176):
-fcm make: build: fix creation of Fortran interface files where procedure
-arguments declared with `EXTERNAL` statements were incorrectly matched in
-case-sensitive mode.
-
-[#170](https://github.com/metomi/fcm/pull/170):
-fcm commit: now works in a working copy with *externals*.
-
-[#169](https://github.com/metomi/fcm/pull/169):
-fcm branch-delete: now fails if bad arguments specified.
-
-[#168](https://github.com/metomi/fcm/pull/168):
-fcm branch-diff: `--trac` now works correctly. The `/intertrac/` syntax did not
-appear to work any more. Use `/search?q=` syntax instead.
-
---------------------------------------------------------------------------------
-
-## 2014.12.0 (2014-12-08)
-
-FCM release 22.
-
-### Noteworthy Changes
-
-[#164](https://github.com/metomi/fcm/pull/164):
-fcm build: fix fortran interface generation, broken by
-[#156](https://github.com/metomi/fcm/pull/156).
-
-[#163](https://github.com/metomi/fcm/pull/163):
-fcm merge --reverse: improve logic. It now works with non-standard layout. The
-`--revision=[M:]N` option is no longer compulsory. It now uses the last changed
-revision of the working copy by default.
-
-[#162](https://github.com/metomi/fcm/pull/162):
-fcm-manage-trac-env-session: fix session logic. If a user already has some
-entries in the `session_attribute` table, the old logic will not insert a new
-`name` or `email` for the user. The new logic will only skip the `name` or
-`email` attribute if already set correctly.
-
---------------------------------------------------------------------------------
-
-## 2014.11.0 (2014-11-25)
-
-FCM release 21.
-
-### Noteworthy Changes
-
-[#161](https://github.com/metomi/fcm/pull/161):
-post-commit-bg-notify-who: use branch creator as branch owner if it cannot be
-determined by the branch name.
-
-[#159](https://github.com/metomi/fcm/pull/159),
-[#160](https://github.com/metomi/fcm/pull/160):
-FCM's Subversion wrappers: display error messages when `svn info` commands
-fail.
-
-[#158](https://github.com/metomi/fcm/pull/158):
-fcm make: extract: improve checking of primary location in inherited mode.
-Compare old value with normalised version of new value. E.g. use of location
-keywords and extra slashes at the end of the path will no longer result in a
-configuration conflict.
-
-[#156](https://github.com/metomi/fcm/pull/156):
-fcm extract and fcm build: fix warnings from Perl 5.12+ when parsing
-configuration file.
-
-[#155](https://github.com/metomi/fcm/pull/155):
-fcm make: fix report of no such config file.
-
-[#150](https://github.com/metomi/fcm/pull/150):
-fcm-manage-trac-env-session: improve removal logic.
-
-[#149](https://github.com/metomi/fcm/pull/149):
-svnperms.py: fix bug, alter message override, and add tests.
-
-[#148](https://github.com/metomi/fcm/pull/148):
-Reverse `commit.conf` logic. To verify branch owner, specify
-`verify-branch-owner`.  To notify branch owner, specify `notify-owner`.
-`post-commit-bg` now supports owner notification on trunk commit.
-
-[#147](https://github.com/metomi/fcm/pull/147):
-Use `dd conv=fsync` to create backup and dump to ensure that backup and dump
-data is written to disk before returning a good status.
-
-[#146](https://github.com/metomi/fcm/pull/146):
-fcm merge: basic support for `meld`.
-
---------------------------------------------------------------------------------
-
-## 2014.09.0 (2014-09-17)
-
-FCM release 20.
-
-### Highlighted Changes
-
-[#138](https://github.com/metomi/fcm/pull/138):
-fcm make: build: continue on failure.
-* The build system will continue as much as possible after a failure, and
-  only repeat failed tasks in incremental modes.
-* This change also fixes a problem where the system could lose information
-  after a failure. Tasks that would be run after the failed task would not get
-  their context recorded correctly. In a subsequent incremental build, the
-  system would end up doing more work than necessary.
-
-[#135](https://github.com/metomi/fcm/pull/135):
-fcm make: multiple config files and search paths.
-* You can now specify multiple `-F PATH` options to specify the search paths
-  for locating configuration files specified as relative paths.
-* You can now specify multiple `-f FILE` options.
-* New `include-path` configuration declaration for specifying the search path
-  for configuration files specified as relative paths.
-* Improve CLI argument diagnostics.
-  * The command dies if an argument is missing an equal sign.
-  * Suggest command line syntax if argument ends with `.cfg`.
-
-[#129](https://github.com/metomi/fcm/pull/129),
-[#136](https://github.com/metomi/fcm/pull/136),
-[#143](https://github.com/metomi/fcm/pull/143),
-[#144](https://github.com/metomi/fcm/pull/144):
-Major improvements to the admin sub-system:
-* Improve hook installation.
-  Write, store and housekeep hook logs at `$REPOS/log/`.
-  Clean options for hook installation.
-  Install `svnperms.conf` from repository root.
-  `TZ=UTC` for all hook scripts.
-* Improve diagnostics for hooks.
-  Custom configuations per repositories.
-  Configurable `pre-revprop-change` permissions.
-  Hooks to work best under Subversion 1.8+.
-  Add modified `svnperms.py` in distribution.
-  Trac 0.12+ changeset added and modified notification.
-* Trac URL template.
-* `fcm-add-trac-env`: add Trac comment edit permission.
-* Separate `InterTrac` configurations from `trac.ini` into `intertrac.ini`.
-* Fix usage of `FCM_CONF_PATH` for admin.
-* Improve documentation and logic for admin configuration.
-* Get user info via LDAP or traditional Unix password file.
-* New admin commands:
-  * `fcm-add-svn-repos-and-trac-env`
-  * `fcm-add-svn-repos`
-  * `fcm-manage-trac-env-session`
-* `pre-commit`: optionally block branch create with bad owner.
-* `post-commit-bg`: rename repository dump.
-* `post-commit-bg`: optionally notify branch owner if author is not owner.
-* `post-*` hooks: configurable notification `From:` field.
-* Test batteries for hooks, and selected admin utilities.
-
-### Noteworthy Changes
-
-[#140](https://github.com/metomi/fcm/pull/140):
-fcm mkpatch: Changes required for use with svn 1.8 + other minor bug fixes.
-
-[#139](https://github.com/metomi/fcm/pull/139):
-fcm commit: fail a commit if it includes the `#commit_message#` file.
-
-[#137](https://github.com/metomi/fcm/pull/137):
-fcm merge: basic support for `kdiff3`.
-
-[#129](https://github.com/metomi/fcm/pull/129):
-`fcm commit`/`fcm branch-rm`: fix branch owner test to use correct user ID.
-
---------------------------------------------------------------------------------
-
-## 2014.06.0 (2014-06-10)
-
-### Highlighted Changes
-
--none-
-
-### Noteworthy Changes
-
-[#125](https://github.com/metomi/fcm/pull/125):
-fcm make: build: handle adjacent cyclic dependency correctly.
-
-[#128](https://github.com/metomi/fcm/pull/128):
-Remove unnecessary `-r`, `-w` and `-x` tests to avoid ACL problems.
-Use Perl's `filetest` pragma where necessary to correctly handle ACL.
-
---------------------------------------------------------------------------------
-
-## 2014-04 (2014-04-23)
-
-### Highlighted Changes
-
-[#114](https://github.com/metomi/fcm/pull/#114),
-[#117](https://github.com/metomi/fcm/pull/#117),
-[#118](https://github.com/metomi/fcm/pull/#118):
-fcm make: build: now recognises statements with Fortran
-OpenMP sentinels that affect build dependencies.
-These dependencies are normally ignored.
-However, if a relevant `build.prop{fc.flag-omp}` property is specified, the
-build system will treat these statements as normal dependency statements.
-
-### Noteworthy Changes
-
-[#121](https://github.com/metomi/fcm/pull/#121):
-fcm make: extract via SSH: improve performance by using `find -printf`
-instead of `find -exec stat`.
-
-[#120](https://github.com/metomi/fcm/pull/#120):
-fcm make: build will now correctly handle C source files that has camel
-case names and `main` functions.
-
-[#111](https://github.com/metomi/fcm/pull/#111):
-fcm make: build in inherit mode: fix incorrect success in repeated
-incremental mode.
-
-[#105](https://github.com/metomi/fcm/pull/#105):
-`FCM_CONF_PATH`: new environment variable that can be used to override
-site/user configuration paths.
-
-[#103](https://github.com/metomi/fcm/pull/#103):
-fcm make: extract: detect diff trees that are the same as the base tree.
-
---------------------------------------------------------------------------------
-
-## 2014-03 (2014-03-03)
-
-### Highlighted Changes
-
-[#96](https://github.com/metomi/fcm/pull/#96):
-fcm make: arguments as extra configurations. This change allows the
-`fcm make` command to accept command line arguments. Each argument will be
-appended in order as a new line in the current `fcm-make.cfg`. This allows
-users to override the configuration on the command line.
-
-### Noteworthy Changes
-
-[#101](https://github.com/metomi/fcm/pull/#101):
-fcm make: do not inherit `steps` if it is already set in the current
-configuration. This allows `steps=` to be declared before `use=`.
-
-[#100](https://github.com/metomi/fcm/pull/#100):
-fcm make: reduce memory usage in incremental mode. Invoking `fcm make`
-with many steps was causing Perl to exit with SIGSEGV previously.
-
-[#98](https://github.com/metomi/fcm/pull/#98):
-fcm make: extract: fix ssh location efficiency.
-
-[#93](https://github.com/metomi/fcm/pull/#93):
-fcm make: fix `use=` properties override. This change allows `use=`
-declarations to be placed anywhere in an `fcm-make.cfg` without interfering
-other `*.prop` declarations.
-
-[#92](https://github.com/metomi/fcm/pull/#92):
-fcm branch-create/list: support alternate username using information in
-users' `~/.subversion/servers` file.
-
-[#91](https://github.com/metomi/fcm/pull/#91):
-fcm make: remove config-on-success on failure.
-
---------------------------------------------------------------------------------
-
-## 2014-02 (2014-02-03)
-
-### Highlighted Changes
-
-[#83](https://github.com/metomi/fcm/pull/#83):
-fcm make: build: an initial attempt to support some Fortran 2K features.
-* Recognise `iso_fortran_env` as an intrinsic module.
-* Recognise `use, intrinsic ::` statements.
-* Recognise `class`, `double complex` and `procedure` as types.
-* Recognise new type declaration attributes.
-* Recognise `abstract interface` blocks.
-* Recognise `impure elemental` as a valid function or subroutine attribute.
-* Recognise `submodule` blocks.
-
-### Noteworthy Changes
-
-[#89](https://github.com/metomi/fcm/pull/#89):
-fcm merge, fcm switch, etc: Subversion 1.8 `svn upgrade` command may
-not write a `.svn/entries` file at the working copy root. Several FCM wrappers
-were failing because they were unable to determine the working copy root. This
-is fixed by using the new entry available in Subversion 1.8 `svn info` to
-determine the working copy root.
-
-[#87](https://github.com/metomi/fcm/pull/#87):
-fcm make: build: print sources to targets diagnostics on `-vv` mode and
-in the log.
-
---------------------------------------------------------------------------------
-
-## 2014-01 (2014-01-20)
-
-### Highlighted Changes
-
--none-
-
-### Noteworthy Changes
-
-[#81](https://github.com/metomi/fcm/pull/#81):
-fcm make: build: fix cyclic dependency logic.
-
-[#80](https://github.com/metomi/fcm/pull/#80):
-fcm make: extract: support `extract.location` declarations reset.
-
-[#79](https://github.com/metomi/fcm/pull/#79):
-fcm make: extract: SSH location: ignore dot files.
-
---------------------------------------------------------------------------------
-
-## 2013-12 (2013-12-02)
-
-### Highlighted Changes
-
--none-
-
-### Noteworthy Changes
-
-[#77](https://github.com/metomi/fcm/pull/#77):
-fcm make: mirror and build: fix etc files install. This was broken by
-[#65](https://github.com/metomi/fcm/pull/#65)
-which causes etc files to be installed to `bin/`.
-
-[#74](https://github.com/metomi/fcm/pull/#74):
-Handle date in `svn log --xml`, which may have trailing spaces and lines.
-
---------------------------------------------------------------------------------
-
-## 2013-11 (2013-11-22)
-
-### Highlighted Changes
-
-[#65](https://github.com/metomi/fcm/pull/#65):
-fcm make: support declaration of class default properties using the
-syntax e.g. `build.prop{class,fc}=my-fc`.
-
-[#65](https://github.com/metomi/fcm/pull/#65):
-fcm make: build: support target name as name-space for target properties,
-e.g. `build.prop{fc}[myprog.exe]=my-fc`. N.B. Dependency properties are
-regarded as source properties, and so are not supported by this change.
-
-### Noteworthy Changes
-
-[#73](https://github.com/metomi/fcm/pull/#73):
-fcm mkpatch: use `/usr/bin/env bash` in generated scripts.
-
-[#72](https://github.com/metomi/fcm/pull/#72):
-fcm conflicts: fix incompatibility with SVN 1.8.
-
-[#70](https://github.com/metomi/fcm/pull/#70):
-fcm CLI: support new SVN 1.8 commands.
-
-[#68](https://github.com/metomi/fcm/pull/#68):
-sbin/fcm-backup-\*: hotcopy before verifying the hotcopy.
-
-[#63](https://github.com/metomi/fcm/pull/#63):
-fcm make: log file improvements. Print FCM version in beginning of log
-file.
-
-[#63](https://github.com/metomi/fcm/pull/#63):
-fcm --version: new command to print FCM version.
-
-[#63](https://github.com/metomi/fcm/pull/#63):
-FCM is no longer dependent on the `HTTP::Date` Perl module.
-
---------------------------------------------------------------------------------
-
-## 2013-10 (2013-10-30)
-
-### Highlighted Changes
-
-Changes that have significant impact on user experience.
-
-[#52](https://github.com/metomi/fcm/pull/#52):
-fcm make: build: new properties for C++ source files, separated from
-C source files. File extension for C and C++ source files is rationalised to
-follow what is documented in the GCC manual.
-
-[#50](https://github.com/metomi/fcm/pull/#50),
-[#54](https://github.com/metomi/fcm/pull/#54):
-fcm make: build/preprocess.prop: include-paths/lib-paths/libs:
-New build properties to specify a list of include paths for compile
-tasks, and library paths and libraries for link tasks.
-
-### Noteworthy Changes
-
-Bug fixes and minor enhancements:
-
-[#59](https://github.com/metomi/fcm/pull/#59):
-fcm make: fix invalid cyclic dependency error when `build.prop{dep.o}` is
-declared on the root name-space.
-
-[#58](https://github.com/metomi/fcm/pull/#58):
-fcm make: build: improve diagnostics for duplicated targets and bad values
-in `build.prop{ns-dep.o}` declarations.
-
-[#55](https://github.com/metomi/fcm/pull/#55):
-fcm make: extract: can now extract from a location that is accessible via
-`ssh` and `rsync`.
-
-[#53](https://github.com/metomi/fcm/pull/#53):
-fcm make: `.fcm-make/log` can now be accessed as `fcm-make.log`.
-
-[#51](https://github.com/metomi/fcm/pull/#51):
-FCM documentation: style updated using Bootstrap.
-
---------------------------------------------------------------------------------
-
-## 2013-09 (2013-09-26)
-
-### Highlighted Changes
-
-Changes that have significant impact on user experience.
-
--None-
-
-### Noteworthy Changes
-
-Bug fixes and minor enhancements:
-
-[#45](https://github.com/metomi/fcm/pull/#45):
-An attempt to allow FCM to work under a case insensitive file system.
-
-[#39](https://github.com/metomi/fcm/pull/#39),
-[#40](https://github.com/metomi/fcm/pull/#40),
-[#41](https://github.com/metomi/fcm/pull/#41):
-CM commands are now tested under Subversion 1.8.
-
-[#37](https://github.com/metomi/fcm/pull/#37):
-fcm make: build: fixed hanging of `ext-iface` tasks when there is an
-unbalanced quote or bracket in a relevant Fortran source file.
-
-[#20](https://github.com/metomi/fcm/pull/#20):
-fcm make: build: allow separate linker command and add ability to keep
-the intermediate library archive while linking an executable.
-
-[#19](https://github.com/metomi/fcm/pull/#19):
-added test suite for code management commands to the distribution.
-
-r4955: fcm extract: fix failure caused by the checking of latest version of a
-deleted branch.
-
---------------------------------------------------------------------------------
-
-## FCM-2-3-1 and Prior Releases
-
-See <http://metomi.github.io/fcm/doc/release_notes/>.
Index: ndors/CONTRIBUTING.md
===================================================================
--- /vendors/CONTRIBUTING.md	(revision 10669)
+++ 	(revision )
@@ -1,82 +1,0 @@
-# FCM: How to Contribute
-
-## Report Bugs
-
-Report bugs and request enhancement by opening an issue on
-[FCM issues @ Github](https://github.com/metomi/fcm/issues). If reporting a
-bug, add a recipe for repeating it. If requesting an enhancement,
-describe the use case in detail.
-
-## Contribute Code
-
-All contributions to FCM are made via pull requests against the *master*
-branch of [metomi/fcm](https://github.com/metomi/fcm). New contributors
-should add their details to the [Code Contributors](#code-contributors)
-section of this file as part of their first request. The developer who
-reviews each pull request is responsible for checking that the
-contributor's name is listed in this file before merging the pull request
-into *master*.
-
-## Code Contributors
-
-The following people have contributed to this code under the terms of
-the Contributor Licence Agreement and Certificate of Origin detailed
-below:
-
-* Jim Bolton (Met Office, UK)
-* Andrew Clark (Met Office, UK)
-* Paul Cresswell (Met Office, UK)
-* Martin Dix (CSIRO, Australia)
-* Ben Fitzpatrick (Met Office, UK)
-* Dave Matthews (Met Office, UK)
-* Stephen Oxley (Met Office, UK)
-* Matt Pryor (Met Office, UK)
-* Roddy Sharp (Met Office, UK)
-* Matt Shin (Met Office, UK)
-* Stuart Whitehouse (Met Office, UK)
-
-(All contributors are identifiable with email addresses in the version
-control logs or otherwise.)
-
-## Contributor Licence Agreement and Certificate of Origin
-
-By making a contribution to this project, I certify that:
-
-(a) The contribution was created in whole or in part by me and I have
-    the right to submit it, either on my behalf or on behalf of my
-    employer, under the terms and conditions as described by this file;
-    or
-
-(b) The contribution is based upon previous work that, to the best of
-    my knowledge, is covered under an appropriate licence and I have
-    the right or permission from the copyright owner under that licence
-    to submit that work with modifications, whether created in whole or
-    in part by me, under the terms and conditions as described by
-    this file; or
-
-(c) The contribution was provided directly to me by some other person
-    who certified (a) or (b) and I have not modified it.
-
-(d) I understand and agree that this project and the contribution
-    are public and that a record of the contribution (including my
-    name and email address) is maintained indefinitely and may be
-    redistributed consistent with this project or the licence(s)
-    involved.
-
-(e) I, or my employer, grant to the UK Met Office and all recipients of
-    this software a perpetual, worldwide, non-exclusive, no-charge,
-    royalty-free, irrevocable copyright licence to reproduce, modify,
-    prepare derivative works of, publicly display, publicly perform,
-    sub-licence, and distribute this contribution and such modifications
-    and derivative works consistent with this project or the licence(s)
-    involved or other appropriate open source licence(s) specified by
-    the project and approved by the
-    [Open Source Initiative (OSI)](http://www.opensource.org/).
-
-(f) If I become aware of anything that would make any of the above
-    inaccurate, in any way, I will let the UK Met Office know as soon as
-    I become aware.
-
-(The FCM Contributor Licence Agreement and Certificate of Origin is
-inspired by the Certificate of Origin used by Enyo and the Linux
-Kernel.)
Index: ndors/COPYING
===================================================================
--- /vendors/COPYING	(revision 10669)
+++ 	(revision )
@@ -1,674 +1,0 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-the GNU General Public License is intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.  We, the Free Software Foundation, use the
-GNU General Public License for most of our software; it applies also to
-any other work released this way by its authors.  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights.  Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received.  You must make sure that they, too, receive
-or can get the source code.  And you must show them these terms so they
-know their rights.
-
-  Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
-  For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software.  For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
-  Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so.  This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software.  The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable.  Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products.  If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
-
-  Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish to
-avoid the special danger that patents applied to a free program could
-make it effectively proprietary.  To prevent this, the GPL assures that
-patents cannot be used to render the program non-free.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Use with the GNU Affero General Public License.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License
-    along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-  If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-
-    <program>  Copyright (C) <year>  <name of author>
-    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, your program's commands
-might be different; for a GUI interface, you would use an "about box".
-
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU GPL, see
-<http://www.gnu.org/licenses/>.
-
-  The GNU General Public License does not permit incorporating your program
-into proprietary programs.  If your program is a subroutine library, you
-may consider it more useful to permit linking proprietary applications with
-the library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.  But first, please read
-<http://www.gnu.org/philosophy/why-not-lgpl.html>.
Index: ndors/README.md
===================================================================
--- /vendors/README.md	(revision 10669)
+++ 	(revision )
@@ -1,38 +1,0 @@
-# FCM
-
-[![Build Status](https://travis-ci.org/metomi/fcm.svg?branch=master)](https://travis-ci.org/metomi/fcm)
-[![DOI](https://zenodo.org/badge/6402932.svg)](https://zenodo.org/badge/latestdoi/6402932)
-
-FCM: a modern Fortran build system,
-and wrappers to Subversion for scientific software development
-
-[Installation](http://metomi.github.io/fcm/doc/installation/) |
-[User Guide](http://metomi.github.io/fcm/doc/user_guide/) |
-[How to Contribute](CONTRIBUTING.md)
-
-## Copyright and Terms of Use
-
-(C) British Crown Copyright 2006-17 Met Office.
-
-FCM is free software: you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation, either version 3 of the License, or
-(at your option) any later version.
-
-FCM is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License
-along with FCM. If not, see <http://www.gnu.org/licenses/>.
-
-FCM documentation is licensed under the British Open Government
-Licence. See doc/etc/fcm-terms-of-use.html and
-<http://www.nationalarchives.gov.uk/doc/open-government-licence/>
-
-See <http://metomi.github.io/fcm/doc/etc/fcm-terms-of-use.html>.
-
-## Acknowledgement for Non-FCM Work
-
-See [Acknowledgement for Non-FCM Work](ACKNOWLEDGEMENT.md).
Index: ndors/index.html
===================================================================
--- /vendors/index.html	(revision 10669)
+++ 	(revision )
@@ -1,14 +1,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-  <title>FCM</title>
-  <meta http-equiv="refresh" content="0;url=doc/">
-</head>
-
-<body>
-<p>If not automatically redirected, please click
-<a href="doc/">FCM Documentation</a>.</p>
-</body>
-</html>
