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 2016-11-02 10:37:50 -04:00
commit 340809e671
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
4 changed files with 54 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/403_for_windows_installer_download.mdwn Normal file
View file

@ -0,0 +1,23 @@
### Please describe the problem.
As of Nov 2, 2016 1:30AM EST, no Windows installer is to be found in https://downloads.kitenet.net/git-annex/windows/current/. Accessing .exe URI directly yields a 403 error. Not sure if this is a temporary hiccup or a script error somewhere -- pardon if this is not the right channel to report this issue.
### What steps will reproduce the problem?
See https://downloads.kitenet.net/git-annex/windows/current/.
### What version of git-annex are you using? On what operating system?
N/A
### Please provide any additional information below.
N/A
[[!format sh """
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
# End of transcript or log.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes! Worked like a charm on my Mac.

13
doc/bugs/addurl_pathdepth_description_misleading.mdwn Normal file
View file

@ -0,0 +1,13 @@
The description for the *pathdepth* option for *addurl* doesn't match its behaviour (emphasis mine).
> Rather than basing the **filename** on the whole url, this causes a **path** to be constructed, starting at the specified depth within the path of the url.
>
> For example, adding the url http://www.example.com/dir/subdir/bigfile with --pathdepth=1 will use "**dir/subdir/bigfile**", while --pathdepth=3 will use "bigfile".
This isn't how it behaves. It would be more accurate as (emphasis on changes):
> Rather than basing the filename on the whole url, this causes a **filename** to be constructed, starting at the specified depth within the path of the url.
>
> For example, adding the url http://www.example.com/dir/subdir/bigfile with --pathdepth=1 will use "**dir_subdir_bigfile**", while --pathdepth=3 will use "bigfile".
For what I am doing (adding a directory tree with addurl and file:// URLs), I'd actually like the behaviour described (to recreate the tree), but I'm not sure which one was the *intended* behaviour..

10
doc/bugs/addurl_pathdepth_description_misleading/comment_1_e4e0a6e27ba5d7d95468e017ec07fa77._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="CandyAngel"
avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8"
subject="comment 1"
date="2016-11-02T10:03:46Z"
content="""
Sorry, you can ignore this for now. I just noticed I'm using 6.20160613.. the Arch Linux version (in community) is really out of date.
I'll update and confirm if this is actually an issue.
"""]]

8
doc/bugs/addurl_pathdepth_description_misleading/comment_2_888bc4ffd264fbd8d07f07c017dec278._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="CandyAngel"
avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8"
subject="comment 2"
date="2016-11-02T10:37:48Z"
content="""
Tested on 6.20161102-g330c68b and the description/behaviour mismatch still exists.
"""]]