| Age | Commit message (Collapse) | Author |
|---|
|
and absolute paths were given
Commit.create_from_tree: fixed critical bug that would cause it to create a branch named master by default, instead of the reference actually set ( which is master in many, but not all cases )
- in fact it could be detached as well, we would fail ungracefully although we could assume master then ... although we cant really make the decision
Repo.is_dirty: improved its abiility to deal with empty repositories and a missing head. Weird thing is that the test always worked fine with the previous code, but it didn't work for me in a similar situation without this change at least
|
|
|
|
different path in the index than the actual one on disk ( from which the object will be created )
Fixed bug the way newlines were handled, which hopefully fixes occasional hangs as well. It works fine with git 1.7.1
Most of the changes are due to the tab-space conversion - its weird once more as I thought it was all in spaces before ... .
|
|
repo.is_dirty: Will not fail on empty repo ( anymore )
index.entries: will just be empty if the repository is empty
refs: added to_full_path method which can be used to create fully synthetic instances of Reference types, added a test for it
Converted all touched files to spaces, which is why git reports so many changed files. Actually I was thinking every file would use spaces, but apparently not
|
|
on lighthouse.
README/intro.rst: added information about the new repository at github
tree: added marker to indicate that submodules would have to be returned there
|
|
if an unset slot is being deleted.
|
|
Fixed test which required to be on master to work - it now uses the HEAD symbolic ref instead.
|
|
This commit includes
- an update to git.objects.utils:parse_actor_and_date to parse the timezone offset
- updates to the git.objects.Commit and git.objects.Tag objects to support *_tz_offset attributes
- updates to tests in test.git.test_commit and test.git.test_refs to check for appropriate *_tz_offset attributes
|
|
|
|
to paths anymore as it will only append '--' if paths are actually given.
Added unittest to verify this
|
|
previous version was making assumptions that would only be true for old git repositories it sesms. The new version of the algorithm deals with this gracefully.
|
|
data, which becomes important if git-write-tree is supposed to be used
|
|
test.helpers: temporary rw repository creators now set the working dir of the program, easing working with relative paths a lot
|
|
exists. Previously it would just fail
|
|
regarding its parents
|
|
order to make it impossible for threads to overwrite each other if we are talking about miliseconds. This renders plenty of 'special' handling redundant
|
|
|
|
Repo.init: fixed incorrect use of the path which was to optionally specify where to initialize the repository. Update test as well
|
|
available at some point natively, within the git suite
Progress parsing now deals properly with Ascii_Escape characters that are meant for the tty - git might stop sending this at some point, but we can deal with it no matter what
|
|
throughput )
|
|
allowing the keys to contain slashes; adjusted test to check for this
|
|
locks will check whether the lock they wrote truly is theirs - in case threads are racing, this might not be the case. Now this issue will be detected and results in a proper failure
|
|
uses a 'failing' lock file, but now its possible to easily put a blocking lock file in its place
|
|
|
|
caused lockups while waiting for stdout
NOTE: This does not have the desired effect, the issue appears to be somewhere within git, possibly, as git simply does not terminate waiting for something, even if stdout is closed.
|
|
|
|
|
|
based git operations in concurrent environments
|
|
exist more gracefully
Added BlockingLockFile which may be used to wait for the lock according to some criteria
|
|
remote.config: SectionConstraint now knows about set_value and get_value which are new to the GitConfigParser
|
|
improve usability. There was no reason that only 'refs' is shortened, whereas there are 'heads' and 'tags' as well
|
|
|
|
|
|
failure as well, one per failed file
|
|
paths - previously it would run into a code-branch I forgot
|
|
Ref(anytype) Iteration was improved such that automatic filtering now also works for SymbolicReferences ( which only return symbolic refs)
|
|
only really knew heads, now we know references as a common base. The adjustment make the ref system as flexible as it was originally meant to be
|
|
has the same content as the new reference
|
|
the destination contains different data. If it contains the same, the move will work as we can do what the user intended
|
|
cannot be reamed using the git-branch command if they are not in refs/heads, that is in a non-standard refs folder
|
|
queries to the git configuration, returning a value in the proper type. In a way its not supposed to be used as you should know the type of your configuration option or get an exception otherwise
|
|
safer to use in case of bare repositories
|
|
repository was initialized with a .git repository, although it was not bare actually
|
|
non-natural when using it
|
|
index easier
|
|
only paths
diff.__str__: fixed incorrect message generation error
|
|
'Reference' implementation now shares all the code from the SymbolicReference base. This implementation allows to create any reference you'd like without requireing git calls
|
|
object. They are only constrained to be located in the refs/ directory
|
|
the item as well to enable predicates to do more proper checking
|
|
method, improved code performance by disabling the visit-once flag by default for trees, which by nature are not recursive
|
