tree 156fea3f913874849ddb726cae6dc11a6ec23ee8
parent f831c118b9c9e1dd3e857fbe43da7c992c91b20f
author nodirg <56001730+nodirg@users.noreply.github.com> 1622051731 -0700
committer GitHub <noreply@github.com> 1622051731 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgrouTCRBK7hj4Ov3rIwAAlUwIAHXEnptKofoff9ezruixNkGX
 6CAhVX6nLR5w5f33Uo/RHgfJH9UODIOFCn29nFdsngorwQNZVd0vCSPWdS/+LjIJ
 gsJ2yGv0NpHnDeJ7dRfaGGLLuesPAob1zfNEgRI2X2UKuik2Oo/a8DH/VPuJqXaC
 Al99MJIBc23kT/ebDZHjITiZeKFHCSH7gEXN5QuZrmjsw2S88gpS1GxoZJddyx8y
 PiSbwd0sK9Ppjc8q1OQD4Je031SxQ02GFuaqMCTmFXxqFFUza4/25iMlPvWSNGtB
 WgxgVbQ1V7hH2Mwcn/oEIrXv6Joi8p1A+0/HCNy0/+QkRvYrrDa3qszJ/qUBgLo=
 =/1oy
 -----END PGP SIGNATURE-----
 

[cas] Require PathSpec.Path to be absolute (#345)

A future CL with all PathSpec.Allowlist which is a list of
PathSpec.Path's descendants. It makes more sense for such paths to
be relative to PathSpec.Path than to CWD, but it would be confusing to
have/allow one struct (PathSpec) to contais paths relative to different
dirs.