| Age | Commit message (Collapse) | Author |
|
|
|
|
|
be done here
|
|
Needs plenty of work
|
|
This fixes a bug when parsing blame -p output: Full commit info headers
only appear for the first line from a particular commit, but other lines
were ignored as the blame info dict was reset after each line.
This patch handles both multiple consecutive lines from a commit and
interleaved lines from multiple commits.
Added real test to verify blame works against the actual commit, not
only a mock of what was produced by blame in old git releases
|
|
implemented now - depending on the performance, it might actually receive some more work
|
|
|
|
everything from the existing implementation, but one by one things can be reimplmented to use dulwich.
It also shows that py 2.6 is quite plagued from its new feature, which is actually a bug, as objects inability to accept any args makes mixins hard to use ...
|
|
module was not found. Its actually a nice mix between decorators which are class types, and a mixin as a metaclass, which applies said decorator. The InstanceDecorator wouldn't actually be needed, but it adds flexibility. Maybe it should be removed ...
|
|
surface while integrating this
|
|
#24, #25
|
|
figured out that the implementation really should be specific to the git command. This leaves the interface open for other implemntations which use a different way to provide feedback (as we do not make assumptions about the format of a feedback line)
|
|
false positives in repositories that are freshly checked out
|
|
tests need some more work. Also, the tests need to be reorganized and move closer to their actual location within gitpython. Hence the refs tests go to git.test.refs, etc
|
|
|
|
|
|
|
|
the test suggests. Pure python implementation still has some trouble, but this should be very fixable
|
|
of the new database types. This reduces code duplication to the mere minimum, but allows custom tests to be added on top easily and flexibly
|
|
|
|
Then the tests will need some work
|