- Oct 14, 2016
-
-
Florian Heck authored
-
Florian Heck authored
-
- Oct 12, 2016
-
-
Florian Heck authored
closes #1
-
Georg Seibt authored
Correctly add new Commit objects to the commit map. put(...) returns the previously associated value leading to commits being overwritten. Using computeIfAbsent(...) does not add Commits multiple times and prevents empty Optionals in the first invocation.
-
- Oct 11, 2016
-
-
Florian Heck authored
-
Florian Heck authored
-
Florian Heck authored
-
Florian Heck authored
-
Florian Heck authored
-
Florian Heck authored
-
Florian Heck authored
-
Georg Seibt authored
-
Georg Seibt authored
-
- Oct 10, 2016
-
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
fix: empty commit was produced if there were no merge commits (String::split produced a 1 element array for an empty string)
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
- Oct 09, 2016
-
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
remove contains check in Repository::checkout (problematic in conjunction with the copy method and the git call will fail anyway if the commit id is invalid), copy commits in Repository::copy
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-
Georg Seibt authored
-