You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is needed for commands like git-commit and git-commit-tree in order to be able to specify author and committer information. While git-commit does provide the --author and --date to specify author information, there are no options for specifying committer information, and git-commit-tree is wholly dependent on environment variables.
For instance, the following code fails with TypeError: type object got multiple values for keyword argument 'env'.
@bpoldrack Two reasons, one technical and the other semantic.
with custom_environment( ... ) isn't thread-safe. I'm using this in a threaded context, and having to manage creating separate Git instances per-thread adds extra complexity.
It's not really the 'right' way to do it in my use case, as the author and committer data are genuinely parameters rather than configuration information for my use case - I'm copying existing information from another VCS over to git, not creating new info.
This is needed for commands like
git-commit
andgit-commit-tree
in order to be able to specify author and committer information. Whilegit-commit
does provide the--author
and--date
to specify author information, there are no options for specifying committer information, andgit-commit-tree
is wholly dependent on environment variables.For instance, the following code fails with
TypeError: type object got multiple values for keyword argument 'env'
.The text was updated successfully, but these errors were encountered: