summaryrefslogtreecommitdiff
path: root/git/db/cmd
Commit message (Collapse)AuthorAgeFilesLines
* Fix issue #41: repo.is_dirty() on empty repository with stashed filesJan Vcelak2014-09-291-2/+2
|
* Fix `git push` hanging when stdout/stderr is bigMarc Abramowitz2014-08-131-3/+3
| | | | Fixes GH-145
* Autopep8 fixes with maximum line length 120Craig Northway2014-07-252-192/+209
|
* Fix for untracked_files no longer detected #138Maximiliano Curia2014-05-061-15/+14
|
* tabs to 4 spaces - overall state of this branch is desolate, but fixable. ↵Sebastian Thiel2014-02-092-808/+808
| | | | Needs plenty of work
* Fixed consecutive lines with same blame info not appearing in blame.Mark Nevill2011-07-181-2/+5
| | | | | | | | | | | | 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
* Fetch info can now deal much better with non-default ref specs, see #23, ↵Sebastian Thiel2011-07-041-2/+29
| | | | #24, #25
* Made remote line parsing more stable. On windows it can be that we encounter ↵Sebastian Thiel2011-06-131-1/+12
| | | | partial or intermixed lines from the pipe. This really shouldn't be, but its windows so it happens
* Added additional opcodes to remote progress to make it compatible to newer ↵Sebastian Thiel2011-06-071-13/+23
| | | | 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
* The --progress flag will now automatically be used if possible when doing ↵Sebastian Thiel2011-06-071-4/+14
| | | | any push or fetch operation
* First run in order to fix the remote handling. Cleaned up interfaces and ↵Sebastian Thiel2011-06-071-65/+140
| | | | 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)
* clone and clone_from methods now support the RemoteProgress interface, using ↵Sebastian Thiel2011-06-071-102/+105
| | | | similar functionality as used by the fetch, push and pull methods
* Fixed fetch/push/pull implementation. Next up is to integrate the ↵Sebastian Thiel2011-06-071-7/+11
| | | | consolidation changes from master to make clone use the same facilities
* Streams returned by git cmd db are now containing all the data right away. ↵Sebastian Thiel2011-06-061-3/+10
| | | | This could cause several copies to exist, and makes the cmd implementation a bad choice if big files are involved
* git cmd implementation of repository appears to work, at least this is what ↵Sebastian Thiel2011-05-302-24/+19
| | | | the test suggests. Pure python implementation still has some trouble, but this should be very fixable
* Fixed tests far enough to allow basic repository tests to be applied to any ↵Sebastian Thiel2011-05-303-8/+20
| | | | 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
* Finished moving all repository methods to the respective interfaces and ↵Sebastian Thiel2011-05-303-806/+712
| | | | | | 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
* Intermediate commit with quite some progress in order to put all extra ↵Sebastian Thiel2011-05-292-5/+388
| | | | 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
* Started to fix imports - tests still have no chance to work as database ↵Sebastian Thiel2011-05-062-15/+13
| | | | changed drastically. Now the actual work begins
* replaced all gitdb strings with gitSebastian Thiel2011-05-061-8/+8
|
* Added all code from gitdb to gitpython. Next is to make it generally work. ↵Sebastian Thiel2011-05-052-0/+438
Then the tests will need some work
View Lorry Controller Status