| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| | |
Do this:
>>> repo.description = "Foo Bar"
>>> repo.description
'Foo Bar'
|
| | |
| |
| |
| |
| |
| |
| | |
Now you can do this:
>>> exported = repo.daemon_export
>>> repo.daemon_export = True
|
| | |
| |
| |
| |
| | |
It is better to have an explicit list of variables for the constructors,
be it only to avoid mispelled arguments.
|
| | |
| |
| |
| | |
It doesn't use an object's private contents, so let's go...
|
| | |
| |
| |
| |
| | |
It is rather intuitive to consider trees as a dict of objects (like
a directory could be seen as a dict of files).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a simplification of the tree baking code.
As a matter of consequency, Tree.construct() and
tree.construct_initialize() have been killed, and repo.tree() has lost
the "paths" argument. This is not a problem since one can just have the
same result with:
dict(k, o for k, o in tree.items() if k in paths)
|
| | |
| |
| |
| |
| |
| |
| | |
It seems more natural to use a dictionnary for directories, since we
usually want to access them by name, and entry order is not relevant.
Also, finding a particular blob given its name is O(1) instead of O(N).
|
| |\ \
| |/ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This adds a testcase for Commit.list_from_string to ensure that
it can properly parse the output of git rev-list --bisect-all.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Rui Abreu Ferrerira pointed out that "git rev-list --bisect-all"
returns a slightly different format which we can easily accomodate
by changing the way we parse rev-list output.
http://groups.google.com/group/git-python/browse_thread/thread/aed1d5c4b31d5027
This resolves the issue mentioned in that thread.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
| |
One bug remaining: git on windows is returning status 0 for `git this-does-not-exist`, so no GitCommandError is raised.
|
| |
|
|
| |
(cherry picked from commit 80f8a18a69e307f6ea0bfeb14791fc75e239faa2)
|
| |
|
|
| |
(cherry picked from commit 1f9e1bacb65fe503ad23efba7f99ca6346fa648c)
|
| | |
|
| |
|
|
| |
(cherry picked from commit ccca12ee26e40fb4c4df2d77154ed496144569b9)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
http://groups.google.com/group/git-python/browse_thread/thread/62b972d2345c74c2?hl=en# and added lines to the per file stats
|
| |
|
|
| |
http://groups.google.com/group/git-python/browse_thread/thread/b8f3580abf31f9db?hl=en# and passed Git a working_tree again (sort of).
|
| | |
|
| | |
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
removed the combined output of stderr and stdout.
Also renamed with_status to extended_output.
The method_missing function needs to be modified, as it does a kwargs.pop(xxx, None); which resulted in with_excpetions=None -> False all the time...
Test should follow tomorrow.
|
| |\ \ \
| | |/
| |/| |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Having execute() use a different directory is an important piece
of API information so I added more documentation about it and
renamed the flag to just "keep_cwd" since that's shorter and simpler.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* commit 'sverre/master':
Added a with_keep_cwd option
Improved the GIT_PYTHON_TRACE=full output format
Added /dist to .gitignore
Conflicts:
lib/git/cmd.py
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When executing commands, if the with_keep_cwd option is
specified, the current working directory will be set to
os.getcwd() instead of the directory containing the
.git directory.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It now also shows stderr if there was any on it, and only
shows stdout if there was any output. Also added a '->'
between the command and the return value as a visual clue.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In order to avoid the expense of parsing .git/config
just to know whether or not a repository is bare
at __init__ time, we just pass an optional flag to
Git.__init__():
bare_repo with a default value of False.
Repo.init_bare() was updated to pass this flag.
We could have an optional Git.read_bare_status() function
that does the expensive lookup. Then, users can optionally
call it at runtime if they really need to know whether or not
a repository is bare. That seems like a decent tradeoff between
speed, correctness, and common use cases.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a fix on top of Govind's latest performance improvement.
self._cwd was always set to self._git_dir which means
a lot of commands that require work trees were not available
to GitPython. Execute now uses self._cwd which is equal to
self._git_dir by default, and self.get_work_tree() if a work tree
exists.
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: David Aguilar <davvid@gmail.com>
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Calling git to find the git_dir and work_tree is very costly.
This patch uses the same mechanisim to find the git_dir as native
git does without shelling out.
Signed-off-by: Govind Salinas <blix@sophiasuchtig.com>
|
| | |/
|/|
| |
| | |
didn't reveal it...
|
| |/
|
|
|
|
| |
http://groups.google.com/group/git-python/browse_thread/thread/b8f3580abf31f9db?hl=en#
I'll look at the other one in an hour
|
| | |
|
| | |
|
| | |
|
