README: clarify some cons - stagit-gopher - A git gopher frontend. (mirror) | |
git clone git://bitreich.org/stagit-gopher/ git://enlrupgkhuxnvlhsf6lc3fziv5h2h… | |
Log | |
Files | |
Refs | |
Tags | |
README | |
LICENSE | |
--- | |
commit daa814e5c59ef7dcadfe779b46bd305e0d93f7a1 | |
parent 77efc691c14e0f1c2309b1709d598e0d106124ec | |
Author: Hiltjo Posthuma <[email protected]> | |
Date: Tue, 31 Oct 2017 23:25:47 +0100 | |
README: clarify some cons | |
Diffstat: | |
M README | 17 +++++++++++------ | |
1 file changed, 11 insertions(+), 6 deletions(-) | |
--- | |
diff --git a/README b/README | |
@@ -136,15 +136,20 @@ Cons | |
---- | |
- Not suitable for large repositories (2000+ commits), because diffstats are | |
- an expensive operation. | |
+ an expensive operation, the cache (-c flag) is a workaround for this in | |
+ some cases. | |
+- Not suitable for large repositories with many files, because all files are | |
+ written for each execution of stagit. This is because stagit shows the lines | |
+ of textfiles and there is no "cache" for file metadata (this would add more | |
+ complexity to the code). | |
- Not suitable for repositories with many branches, a quite linear history is | |
assumed (from HEAD). | |
- Relatively slow to run the first time (about 3 seconds for sbase, | |
1500+ commits), incremental updates are faster. | |
- Does not support some dynamic features like: | |
- - snapshot tarballs. | |
- - file tree per commit. | |
- - history log of branches diverged from HEAD. | |
- - stats (git shortlog -s). | |
+ - Snapshot tarballs per commit. | |
+ - File tree per commit. | |
+ - History log of branches diverged from HEAD. | |
+ - Stats (git shortlog -s). | |
- this is by design, just use git locally. | |
+ This is by design, just use git locally. |