Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | adjust: If the adjusted branch already exists, avoid overwriting it, since ↵ | 2016-05-13 | |
| | | | | | | | | | | | | | | | | | it might contain changes that have not yet been propigated to the original branch. Could not think of a foolproof way to detect if the old adjusted branch was just behind the current branch. It's possible that the user amended the adjusting commit at the head of the adjusted branch, for example. I decided to bail in this situation, instead of just entering the old branch, so that if git annex adjust succeeds the user is always in a *current* adjusted branch, not some old and out of date one. What could perhaps be done is enter the old branch and then update it. But that seems too magical; the user may have rebased master or something or may not want to propigate the changes from the old branch. Best to error out. | ||
* | found a bad memory use in git | 2016-05-12 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2016-05-12 | |
|\ | |||
* | | devblog | 2016-05-12 | |
| | | |||
| * | Added a comment: v6 mode | 2016-05-12 | |
| | | |||
| * | (no commit message) | 2016-05-12 | |
|/ | |||
* | webapp: Avoid confusing display of dead remotes. | 2016-05-12 | |
| | |||
* | followup | 2016-05-12 | |
| | |||
* | response | 2016-05-12 | |
| | |||
* | comment | 2016-05-12 | |
| | |||
* | open bug from forum post | 2016-05-12 | |
| | |||
* | response | 2016-05-12 | |
| | |||
* | response | 2016-05-12 | |
| | |||
* | response | 2016-05-12 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2016-05-12 | |
|\ | |||
* | | link to my post "proposal for extending smudge/clean filters with raw file ↵ | 2016-05-12 | |
| | | | | | | | | access" | ||
| * | Added a comment | 2016-05-12 | |
| | | |||
| * | Added a comment | 2016-05-12 | |
| | | |||
| * | Added a comment | 2016-05-12 | |
| | | |||
| * | (no commit message) | 2016-05-12 | |
| | | |||
| * | (no commit message) | 2016-05-11 | |
| | | |||
| * | Added a comment | 2016-05-11 | |
|/ | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2016-05-11 | |
|\ | |||
* | | Change git annex info remote encryption description to use wording closer to ↵ | 2016-05-11 | |
| | | | | | | | | what's used in initremote. | ||
* | | clarify some things | 2016-05-11 | |
| | | | | | | | | | | | | | | In particular, specifying multiple keyid= in enableremote/initremote doesn't work, and never has AFAICS, so don't suggest using it. Also, there was some public/private key wording confusion. | ||
| * | (no commit message) | 2016-05-11 | |
|/ | |||
* | add news item for git-annex 6.20160511 | 2016-05-11 | |
| | |||
* | prep release6.20160511 | 2016-05-11 | |
| | |||
* | rename ↵ | 2016-05-11 | |
| | | | | forum/__34__git_annex_assitant_--stop__34___doesn__39__t_work_in_OSX_10.11.4.mdwn to forum/__34__git_annex_assistant_--stop__34___doesn__39__t_work_in_OSX_10.11.4.mdwn | ||
* | (no commit message) | 2016-05-11 | |
| | |||
* | Fix typo | 2016-05-11 | |
| | |||
* | Bug report. | 2016-05-11 | |
| | |||
* | Added a comment: git-annex on windows additional | 2016-05-10 | |
| | |||
* | git-annex visibility on windows | 2016-05-10 | |
| | |||
* | Added a comment | 2016-05-10 | |
| | |||
* | typo | 2016-05-10 | |
| | |||
* | typo | 2016-05-10 | |
| | |||
* | rename to legal ikiwiki filename | 2016-05-10 | |
| | |||
* | devblog | 2016-05-10 | |
| | |||
* | close; done in v6 mode | 2016-05-10 | |
| | |||
* | close | 2016-05-10 | |
| | |||
* | close | 2016-05-10 | |
| | |||
* | response | 2016-05-10 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2016-05-10 | |
|\ | |||
* | | Added new encryption=sharedpubkey mode for special remotes. | 2016-05-10 | |
| | | | | | | | | | | | | This is useful for makking a special remote that anyone with a clone of the repo and your public keys can upload files to, but only you can decrypt the files stored in it. | ||
| * | Added a comment | 2016-05-10 | |
|/ | |||
* | In the unusual configuration where annex.crippledfilesystem=true but ↵ | 2016-05-10 | |
| | | | | | | | core.symlinks=true, store object contents in mixed case hash directories so that symlinks will point to them. Contents are searched for in both locations, same as before, so this does not add any overhead. | ||
* | improve comment | 2016-05-10 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2016-05-10 | |
|\ | |||
* | | update | 2016-05-10 | |
| | |