Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
e0c02c8621
4 changed files with 50 additions and 0 deletions
|
@ -0,0 +1,14 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="209.250.56.55"
|
||||
subject="comment 7"
|
||||
date="2014-07-03T19:03:52Z"
|
||||
content="""
|
||||
That lubuntu bug explains why git-annex would not autostart on login.
|
||||
|
||||
However, that does not explain the original problem description, which was that the `Make Repository` button seemed to make a repository but not switch to the webapp running in that repository. In the case of making a new repository, the webapp is started in it by git-annex, not by the desktop autostart mechanism.
|
||||
|
||||
Can you reproduce the original problem?
|
||||
|
||||
|
||||
"""]]
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="209.250.56.55"
|
||||
subject="comment 1"
|
||||
date="2014-07-03T19:14:37Z"
|
||||
content="""
|
||||
Encrypted [[special_remotes]] are supported just fine on Android.
|
||||
|
||||
As for storing the [[encrypted git repository itself on a remote|special_remotes/gcrypt]], which is what git-remote-gcrypt is used for, it would need porting that to Android. I don't think that should be very hard (it's just a rather complicated shell script and all the tools it uses are already included in the git-annex bundle). I may eventully end up reimplementing git-remote-gcrypt as part of git-annex in Haskell, since porting it to eg, Windows is likely to be a lot harder..
|
||||
"""]]
|
|
@ -0,0 +1,14 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="209.250.56.55"
|
||||
subject="comment 3"
|
||||
date="2014-07-03T19:20:49Z"
|
||||
content="""
|
||||
\"67e69242-d57c-4b50-aaf9-74876b899962\" is the UUID of a git annnex repository that git-annex has on record as containing the file. Since it does not have a description set (which normally gets done automatically when setting up the repository), and is not one of the remotes of the repository where you ran `git annex whereis`, it's a bit hard to tell what repository that is.
|
||||
|
||||
What I would do in this situation is:
|
||||
|
||||
1. Look around my computers for a repository with that UUID. You can run this command in a repository to see its uuid: `git config annex.uuid`
|
||||
2. If I found it, I'd run `git annex describe here \"something sensible\"` and maybe set it up as a remote of other repositories and then `git annex drop` the data from it if desired.
|
||||
3. If I was unable to find the repository, I might assume it was one I created before, and have removed. Then I'd tell git-annex that: `git annex dead 67e69242-d57c-4b50-aaf9-74876b899962` (if it turns out I was wrong and the repository turns up later, this can always be reversed by running `git annex semitrust 67e69242-d57c-4b50-aaf9-74876b899962`)
|
||||
"""]]
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="209.250.56.55"
|
||||
subject="comment 1"
|
||||
date="2014-07-03T19:10:53Z"
|
||||
content="""
|
||||
To make git-annex output the key of a file, run: `git annex lookupkey $file`
|
||||
|
||||
I don't know if the git-annex key is appropriate for your use-case. If the files never get changed, then it's a nice stable identifier. If ongoing changes are made to a file, and you want to link to the most recent version, the key would not be useful.
|
||||
|
||||
You might also look at git-annex's [[metadata]]; you could make up some metadata field and value and attach it to a file, and it would persist as the file was modified.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue