| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Fixes GH-145
|
|
|
|
|
|
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
|
|
tests only work reliably in a patched up version, or the next point release.
|
|
implemented now - depending on the performance, it might actually receive some more work
|
|
enough for the first batch of work
|
|
actually
|
|
inefficient, but can't help it. Basic repo tests don't work as dulwich ignores alternate files
|
|
least, which implicitly includes pack handling. For the pack specific tests to work, one would need a pack interface though, which is currently not planned to be specifically exposed
|
|
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 ...
|
|
surface while integrating this
|
|
|
|
#24, #25
|
|
partial or intermixed lines from the pipe. This really shouldn't be, but its windows so it happens
|
|
git versions. This bug existed for quite a while but didn't show up as progress wasn't sent most of the time. All methods that could use a progress will only activate it if a progress is actually given
|
|
any push or fetch operation
|
|
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)
|
|
similar functionality as used by the fetch, push and pull methods
|
|
consolidation changes from master to make clone use the same facilities
|
|
This could cause several copies to exist, and makes the cmd implementation a bad choice if big files are involved
|
|
command implementations. The previous performance test was truncated a bit as it compared directly with the git hash_object write performance. This is out, and if we wanted it we could implement it , but its actually slower for us
|
|
|
|
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
|
|
implementations. It seems theoretically work together now, although it clearly is much more complex than ever before.
The repo package was slimmed down to being a module once again, which is only there for compatability actually
|
|
methods on the default Repo implementation into interfaces or something that can be abstracted. It shows that it would indeed be good to keep the differentiation between Repositories which contain an object database as it is clearly easier to setup any combination of repositories that use git and those that do not, with just the addition of one more level of indirection. Lets see how it will end up
|
|
repo interface. Added submodule interface ... goal is to provide all of the extra repo functionality in custom interfaces
|
|
changed drastically. Now the actual work begins
|
|
|
|
Then the tests will need some work
|
