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 2013-07-11 19:27:35 -04:00
commit a082ab03b6
3 changed files with 34 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/bugs/__96__git_annex_fix__96___run_on_non-annexed_files_is_no-op/comment_2_d11744202213d6f897f4234bc4c70c18._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
nickname="Richard"
subject="comment 2"
date="2013-07-11T20:18:44Z"
content="""
I wanted to use it as a way to prepare the files before running `git annex add`. I like to have everything exactly how I want it before I add anything to git, or git-annex. Does git-annex do anything in the git-annex branch prior to running the pre-commit hook? I.e. is there any penalty, however slight, in running `git annex add` several times while moving stuff around?
"""]]

17
doc/bugs/wishlist:_generic_annex.cost-command.mdwn Normal file
View file

@ -0,0 +1,17 @@
### Current setup
ATM git-annex has
remote.<name>.annex-cost
remote.<name>.annex-cost-command # command is not provided cmdline options by annex
to set the cost for a given remote. That requires setting up one of those variables per each host, and possibly hardcoding options for the annex-cost-command providing e.g. the remote name.
### Suggestion
wouldn't it be more general and thus more flexible to have a repository-wide
annex.cost-command
which could take options %remote, %file and assessed accordingly per each file upon '--get' request to allow maximal flexibility: e.g. some files might better be fetched from remotes supporting transfer compression, some from the web, etc. Also it might be worth providing %remote_kind ("special" vs "git") to disambiguate %remote's?

8
doc/forum/not_getting_file_contents/comment_2_dc7403e1b551552f9fd00da6a1453570._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="trilobite"
ip="71.17.134.14"
subject="comment 2"
date="2013-07-11T23:23:41Z"
content="""
I did this with local synch in home lan. Filenames do travel both directions. Just not contents. They are identifed as symlinks rather than files.
"""]]