| Age | Commit message (Collapse) | Author |
|---|
|
|
|
working directory.
A working directory is dirty if it has any uncommitted changes (in the working
directory or in the index). Bare repositories are by nature always clean.
|
|
Do this:
>>> repo.description = "Foo Bar"
>>> repo.description
'Foo Bar'
|
|
Now you can do this:
>>> exported = repo.daemon_export
>>> repo.daemon_export = True
|
|
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)
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit 80f8a18a69e307f6ea0bfeb14791fc75e239faa2)
|
|
|
|
http://groups.google.com/group/git-python/browse_thread/thread/b8f3580abf31f9db?hl=en# and passed Git a working_tree again (sort of).
|
|
|
|
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>
|
|
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>
|
|
|
|
|
|
|
|
|
|
up tests so they pass except for stderr test. Modified version information retrieval.
|
