summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAge
* roadmap update5.20151019Gravatar Joey Hess2015-10-19
|
* responseGravatar Joey Hess2015-10-19
|
* commentGravatar Joey Hess2015-10-19
|
* responseGravatar Joey Hess2015-10-19
|
* Added a commentGravatar ovidiu@66ace8a8d99ce938b0538ffa0f26d30db02a96262015-10-19
|
* Added a commentGravatar darkfeline2015-10-18
|
* (no commit message)Gravatar ovidiu@66ace8a8d99ce938b0538ffa0f26d30db02a96262015-10-18
|
* Added a commentGravatar darkfeline2015-10-18
|
* Added a comment: Replicating my key for encrypted special remotesGravatar craig@6ddb6e2c94325e18a0d631a06e63fdc111ab1f122015-10-17
|
* Added a commentGravatar ovidiu@66ace8a8d99ce938b0538ffa0f26d30db02a96262015-10-17
|
* Added a comment: amazingGravatar anarcat2015-10-17
|
* Added a commentGravatar PaulK2015-10-16
|
* devblogGravatar Joey Hess2015-10-15
|
* upstream patch needs testingGravatar Joey Hess2015-10-15
|
* followupGravatar Joey Hess2015-10-15
|
* close as encfs is the bugGravatar Joey Hess2015-10-15
|
* fixedGravatar Joey Hess2015-10-15
|
* Avoid displaying network transport warning when a ssh remote does not yet ↵Gravatar Joey Hess2015-10-15
| | | | | | | | | | | have an annex.uuid set. Instead, only display transport error if the configlist output doesn't include an annex.uuid line, even an empty one. A recent change made git-annex init try to get all the remote uuids, and so the transport error would be displayed by it. It was also displayed when eg, copying files to a remote that had no uuid yet.
* responseGravatar Joey Hess2015-10-15
|
* responseGravatar Joey Hess2015-10-15
|
* closeGravatar Joey Hess2015-10-15
|
* analysisGravatar Joey Hess2015-10-15
|
* commentGravatar Joey Hess2015-10-15
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2015-10-15
|\
| * Added a commentGravatar CandyAngel2015-10-15
| |
| * Added a comment: renaming oesn't work as expected when changing the extensionGravatar ptspts@d0db5f2b8c4e6befae8899f31c117d093913f43e2015-10-15
| |
| * (no commit message)Gravatar PaulK2015-10-15
| |
| * (no commit message)Gravatar PaulK2015-10-15
| |
| * (no commit message)Gravatar PaulK2015-10-15
| |
| * (no commit message)Gravatar https://me.yahoo.com/a/egXXJdRkj_WkxY8aXA9cdIu2fQc-#a61c12015-10-14
| |
| * (no commit message)Gravatar https://me.yahoo.com/a/egXXJdRkj_WkxY8aXA9cdIu2fQc-#a61c12015-10-14
| |
| * (no commit message)Gravatar https://me.yahoo.com/a/egXXJdRkj_WkxY8aXA9cdIu2fQc-#a61c12015-10-14
| |
| * (no commit message)Gravatar https://me.yahoo.com/a/egXXJdRkj_WkxY8aXA9cdIu2fQc-#a61c12015-10-14
| |
| * (no commit message)Gravatar https://me.yahoo.com/a/egXXJdRkj_WkxY8aXA9cdIu2fQc-#a61c12015-10-14
| |
| * (no commit message)Gravatar https://me.yahoo.com/a/egXXJdRkj_WkxY8aXA9cdIu2fQc-#a61c12015-10-14
| |
* | word wrapGravatar Joey Hess2015-10-14
|/
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2015-10-14
|\
* | Changed drop ordering when using git annex sync --content or the assistant, ↵Gravatar Joey Hess2015-10-14
| | | | | | | | to drop from remotes first and from the local repo last. This works better with the behavior changes to drop in many cases.
| * timing infoGravatar anarcat2015-10-13
| |
| * Added a commentGravatar https://me.yahoo.com/a/FHnTlSBo1eCGJRwueeKeB6.RCaPbGMPr5jxx8A--#ce0d82015-10-13
| |
| * more notesGravatar anarcat2015-10-13
| |
| * workaroundsGravatar anarcat2015-10-13
|/
* clarificationGravatar anarcat2015-10-13
|
* Added a commentGravatar darkfeline2015-10-13
|
* new bugGravatar Antoine Beaupré2015-10-13
|
* (no commit message)Gravatar darkfeline2015-10-13
|
* doc/devblog/day_322-326__concurrent_drop_safety.mdwn: WordingGravatar Richard Hartmann2015-10-12
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2015-10-12
|\
* | responseGravatar Joey Hess2015-10-12
| |
* | Avoid unncessary write to the location log when a file is unlocked and then ↵Gravatar Joey Hess2015-10-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | added back with unchanged content. Implemented with no additional overhead of compares etc. This is safe to do for presence logs because of their locality of change; a given repo's presence logs are only ever changed in that repo, or in a repo that has just been actively changing the content of that repo. So, we don't need to worry about a split-brain situation where there'd be disagreement about the location of a key in a repo. And so, it's ok to not update the timestamp when that's the only change that would be made due to logging presence info.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-01 02:15:21 +0000