delta/python-packages/gitpython.git, branch 3.1.9 github.com: gitpython-developers/GitPython.git Bump patch level 2020-10-01T03:18:13+00:00 Sebastian Thiel sebastian.thiel@icloud.com 2020-10-01T03:18:13+00:00 7cd47aeea822c484342e3f0632ae5cf8d332797d 






rename sublist to subset
2020-09-29T06:24:10+00:00

Sagi Shadur
saroad2@gmail.com

2020-09-29T06:19:50+00:00

60acfa5d8d454a7c968640a307772902d211f043












Rename get_ignored to ignored and fix the documentation
2020-09-29T06:24:10+00:00

Sagi Shadur
saroad2@gmail.com

2020-09-29T05:53:40+00:00

e2067ba536dd78549d613dc14d8ad223c7d0aa5d












Find paths ignored in .gitignore
2020-09-29T06:24:10+00:00

Sagi Shadur
saroad2@gmail.com

2020-09-28T20:05:29+00:00

df6fa49c0662104a5f563a3495c8170e2865e31b












Add venv to gitignore
2020-09-29T06:23:20+00:00

Sagi Shadur
saroad2@gmail.com

2020-09-29T06:20:47+00:00

8a9f8c55d6a58fe42fe67e112cbc98de97140f75












git/repo/base.py: is_dirty(): Fix pathspec handling
2020-09-28T12:39:17+00:00

Arnaud Patard
apatard@hupstream.com

2020-09-28T12:24:33+00:00

624eb284e0e6edc4aabf0afbdc1438e32d13f4c9

It's possible to specify a pathspec (eg :!foo) to git diff/status/...
but it currently fails with:

git.exc.GitCommandError: Cmd('/usr/bin/git') failed due to: exit code(128)
  cmdline: /usr/bin/git diff --abbrev=40 --full-index --raw :!foo
  stderr: 'fatal: ambiguous argument ':!foo': unknown revision or path not in the working tree.

Add missing '--' to the arguments to fix this ambiguity

Signed-off-by: Arnaud Patard <apatard@hupstream.com>





It's possible to specify a pathspec (eg :!foo) to git diff/status/...
but it currently fails with:

git.exc.GitCommandError: Cmd('/usr/bin/git') failed due to: exit code(128)
  cmdline: /usr/bin/git diff --abbrev=40 --full-index --raw :!foo
  stderr: 'fatal: ambiguous argument ':!foo': unknown revision or path not in the working tree.

Add missing '--' to the arguments to fix this ambiguity

Signed-off-by: Arnaud Patard <apatard@hupstream.com>







Fix typo
2020-09-09T15:10:40+00:00

Eric Dill
thedizzle@gmail.com

2020-09-09T14:07:40+00:00

135e7750f6b70702de6ce55633f2e508188a5c05












Update release verification instructions as suggested in #1055
2020-09-07T01:24:05+00:00

Sebastian Thiel
sebastian.thiel@icloud.com

2020-09-07T01:24:05+00:00

1759a78b31760aa4b23133d96a8cde0d1e7b7ba6












Adjust signature key - please read if you verify installs/packages
2020-09-04T02:00:48+00:00

Sebastian Thiel
sebastian.thiel@icloud.com

2020-09-04T02:00:48+00:00

eb411ee92d30675a8d3d110f579692ea02949ccd

After a recent 'cleanup' operation that attempted to simplify my
GPG key workflow with Yubikeys, it looks like my GPG installation
has 'forgotten' how to interact with the key I typically used
to sign GitPython releases.

Since I never managed to establish a chain of trust with my only
remaining 'good' key, for you this means you cannot trust new
GitPython releases anymore.

There is nothing I can do about except to apologize for the hassle.

If you want to make constructive suggestions on how to fix this, I am
happy to work with you on that.





After a recent 'cleanup' operation that attempted to simplify my
GPG key workflow with Yubikeys, it looks like my GPG installation
has 'forgotten' how to interact with the key I typically used
to sign GitPython releases.

Since I never managed to establish a chain of trust with my only
remaining 'good' key, for you this means you cannot trust new
GitPython releases anymore.

There is nothing I can do about except to apologize for the hassle.

If you want to make constructive suggestions on how to fix this, I am
happy to work with you on that.







bump patch level
2020-09-04T01:54:15+00:00

Sebastian Thiel
sebastian.thiel@icloud.com

2020-09-04T01:54:15+00:00

e7b5e92791dd4db3535b527079f985f91d1a5100