delta/python-packages/gitpython.git/git/objects, branch 2.0.0 github.com: gitpython-developers/GitPython.git Add support for getting "aware" datetime info 2016-04-19T19:52:06+00:00 Vincent Driessen me@nvie.com 2016-04-19T12:27:25+00:00 a2c8c7f86e6a61307311ea6036dac4f89b64b500 This adds 2 properties to commits. Their values are derived from the existing data stored on them, but this makes them more conveniently queryable: - authored_datetime - committed_datetime These return "aware" datetimes, so they are effectively companions to their raw timestamp equivalents, respectively `authored_date` and `committed_date`. These datetime instances are convenient structures since they show the author-local commit date and their UTC offset. 
This adds 2 properties to commits.  Their values are derived from the
existing data stored on them, but this makes them more conveniently
queryable:

    - authored_datetime
    - committed_datetime

These return "aware" datetimes, so they are effectively companions to
their raw timestamp equivalents, respectively `authored_date` and
`committed_date`.

These datetime instances are convenient structures since they show the
author-local commit date and their UTC offset.
fix(tree): show that fixing Tree.cache is not possible 2015-12-14T18:19:19+00:00 Sebastian Thiel byronimo@gmail.com 2015-12-14T18:19:19+00:00 4f1110bd9b00cb8c1ea07c3aafe9cde89b3dbf9b The problem is that a per-tree modification API cannot work properly, as the sorting is based on full paths of all entries within the repository. This feat can only be achieved by the index, which to my knowledge already does it correctly. The only fix is to remove the misleading API entirely, which will happen in the next commit. Related to #369 
The problem is that a per-tree modification API cannot work properly, as the sorting is based
on full paths of all entries within the repository. This feat can only be achieved by the index,
which to my knowledge already does it correctly.

The only fix is to remove the misleading API entirely, which will happen in the next commit.

Related to #369
chore(tree): remove dead code 2015-12-13T12:21:44+00:00 Sebastian Thiel byronimo@gmail.com 2015-12-13T12:21:40+00:00 0de827a0e63850517aa93c576c25a37104954dba [skip ci] 
[skip ci]
fix(tree): tree item sort now uses git-style 2015-12-13T12:10:33+00:00 Sebastian Thiel byronimo@gmail.com 2015-12-13T12:10:33+00:00 d82a6c5ed9108be5802a03c38f728a07da57438e Previously it was possible to generate trees which didn't appear legit to git as gitpython's sorting was a simple alpha-numeric sort. Git uses one that minimizes literal string comparisons though, and thus behaves slightly differently sometimes. Fixes #369 
Previously it was possible to generate trees which didn't
appear legit to git as gitpython's sorting was a simple alpha-numeric
sort. Git uses one that minimizes literal string comparisons though,
and thus behaves slightly differently sometimes.

Fixes #369
fix(commit): respect daylight saving when computing utc-offset 2015-11-08T14:09:41+00:00 Sebastian Thiel byronimo@gmail.com 2015-11-08T14:09:41+00:00 0900a51f986f3ed736d9556b3296d37933018196 Related to #362 
Related to #362
fix(commit): serialization timezone handling 2015-08-17T20:33:02+00:00 Sebastian Thiel byronimo@gmail.com 2015-08-17T20:32:15+00:00 a8f7e3772f68c8e6350b9ff5ac981ba3223f2d43 Previously timezones which were not divisable by 3600s would be parsed correctly, but would serialize into a full hour, rounded up. Now floating point computation is used which fixes the issue. Related to #336 
Previously timezones which were not divisable by 3600s would be
parsed correctly, but would serialize into a full hour, rounded up.

Now floating point computation is used which fixes the issue.

Related to #336
gic {init,clone} --separate-git-dir is supported only since 1.7.5 2015-07-22T11:35:47+00:00 Julien Pivotto roidelapluie@inuits.eu 2015-07-22T07:28:42+00:00 6fdb6a5eac7433098cfbb33d3e18d6dbba8fa3d3 Without this commit the update() function of a submodule does not work in CentOS 6. 
Without this commit the update() function of a submodule does not work
in CentOS 6.
typo in submodules api documentation 2015-07-17T20:10:05+00:00 Julien Pivotto roidelapluie@gmail.com 2015-07-17T20:09:05+00:00 3438795d2af6d9639d1d6e9182ad916e73dd0c37 






Added two extra paramaters for commit to take author date and commit date
2015-07-17T16:28:55+00:00

avi
hi@avi.im

2015-07-17T16:28:55+00:00

141b78f42c7a3c1da1e5d605af3fc56aceb921ab












Added NullHandlers to all loggers to preven "No handler" messages
2015-06-25T13:24:40+00:00

James Nowell
jcnowell@missionfocus.com

2015-06-25T13:24:40+00:00

aa0ccead680443b07fd675f8b906758907bdb415

When the code is run without setting up loggers, the loggers have no
handlers for the emitted messages. The logging module displays:
`No handlers could be found for logger "git.cmd"` on the
console. By adding a NullHandler (a no-op) the message disappears,
and doesn't affect logging when other handlers are configured.





When the code is run without setting up loggers, the loggers have no
handlers for the emitted messages. The logging module displays:
`No handlers could be found for logger "git.cmd"` on the
console. By adding a NullHandler (a no-op) the message disappears,
and doesn't affect logging when other handlers are configured.