mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2012-09-11 01:01:42 -04:00
commit b3f4c6eb68
2 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/design/assistant/android/comment_4_054f06311e2b51d73be569f181eb004f._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="4.153.8.30"
subject="comment 4"
date="2012-09-11T02:12:45Z"
content="""
Thanks Bernard, that's really massively useful. It makes sense -- statically building with libc should work, the Android kernel is still Linux after all.
To get past the iconv problem, I think all you need is part of the `locales` package from your linux system installed on the Android. Probably just a few of the data files from /usr/share/i18n/charmaps/
"""]]

10
doc/forum/one_annex_versus_many_annexes__63__.mdwn Normal file
View file

@ -0,0 +1,10 @@
I'm curious how other people are using git-annex:
* A single annex containing everything they want to keep track of (albeit with some files only available in some remotes).
* Several annexes for different purposes.
I'm mostly asking because I don't want to get too far into using git-annex without thinking clearly about which is the most suitable choice for me. At present I have things split into two annexes, one for things I really wouldn't want to lose (and some of which are somewhat private), and another for comparatively throwaway items. However, given the possibility of setting different annex.numcopies on different file globs or directories, it seems like it might be kind of silly to make my life more complicated by having more than one annex.
Primarily, I'm curious if there are some implications of the decision that I haven't considered. It seems like an obvious point that one would want different annexes is if they're used in distinctly different security-level environments (e.g. I'm happy to copy my FLAC (music) files over to my work computer which lives at the office, but I wouldn't want to copy personal financial documents - or even the filenames - there.)
-Mike