summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorSilvan Mosberger <contact@infinisil.com>2020-03-15 07:17:45 +0100
committerSilvan Mosberger <contact@infinisil.com>2020-04-13 17:27:01 +0200
commitf9e94b9ffee57a20841dbf35d1e96c22cfbcc56e (patch)
tree30f0193907c05a49fde84d3e83abbc0c1175c1b9 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentd3ac6de2d9b36712cfba31c2a363b806badb1b9b (diff)
maintainer-list: Fix missing githubId's
All these IDs were carefully obtained with - If possible, look at which commit introduced the maintainer and check with the GitHub API whether it was the person we think it should be. If yes, that's great - If above doesn't work for any reason (which was the case for about half), then I went through the commit log and through GitHub PRs manually, to see who the person is Sometimes this required trying to find a commit after the svn-era, but before the committer stopped contributing. Sometimes when one person adds two maintainers this required checking that they are known to each other through bidirectional GitHub follows. For tweber's github, see: https://github.com/NixOS/nixpkgs/pull/82461#issuecomment-599433112
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions