| Commit message (Collapse) | Author | Age |
|---|
| |\ |
|
| | |
| |
| |
| | |
run by git-annex.
|
| |\|
| |
| |
| |
| |
| | |
Conflicts:
Locations.hs
debian/changelog
|
| | |
| |
| |
| | |
used for SHA256, so as to not break on systems like Windows that have very small maximum path length limits.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows the git repository to be moved while git-annex is running in
it, with fewer problems.
On Windows, this avoids some of the problems with the absurdly small
MAX_PATH of 260 bytes. In particular, git-annex repositories should
work in deeper/longer directory structures than before. See
http://git-annex.branchable.com/bugs/__34__git-annex:_direct:_1_failed__34___on_Windows/
There are several possible ways this change could break git-annex:
1. If it changes its working directory while it's running, that would
be Bad News. Good news everyone! git-annex never does so. It would also
break thread safety, so all such things were stomped out long ago.
2. parentDir "." -> "" which is not a valid path. I had to fix one
instace of this, and I should probably wipe all calls to parentDir out
of the git-annex code base; it was never a good idea.
3. Things like relPathDirToFile require absolute input paths,
and code assumes that the git repo path is absolute and passes it to it
as-is. In the case of relPathDirToFile, I converted it to not make
this assumption.
Currently, the test suite has 16 failures.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the git version used at build time when running git-checkattr and git-branch remove.
It's ok to probe every time for git-branch remove because that's
run quite rarely. For git-checkattr, it's run only once, when
starting the --batch mode, and so again the overhead is pretty minimal.
This leaves 2 places where the build version is still used.
git merge might be interactive or fail if one skews, and --no-gpg-sign
might not be pased, or might be passed to a git that doesn't understand it
if the other skews. It seems a little expensive to check the git version
each time these are used.
This doesn't seem likely to cause many problems, at least compared with
check-attr hanging on skew.
|
| |
|
|
|
|
|
|
| |
and so fail.
In the case where a remote of the bare repo has a fetch = configuration,
refs/remotes/origin/master will exist, and so the merge code path tried to
run in the bare repo.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Avoids an intractable problem that prevents the pre-commit hook from
telling if such a file is intended to be an annexed file or not.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Getting rid of build warning
warning: 'statfs64' is deprecated: first deprecated in OS X 10.6
[-Wdeprecated-declarations]
10.6 is much older than the oldest git-annex OSX port, so won't break
anything.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
More aggressive rsync params fixup for windows. Param may contain a url, or
a file path, so check if it looks like a local file path and if so, fix it
up.
On windows only, rsyncUrlIsPath will treat c:foo as a path, rather than as
a rsyncurl starting with a host "c".
|
| | |
|
| |
|
|
|
| |
Fixes:
/home/joey/tmp/xxx/.git/annex/misctmp/torrent18347: openFile: resource busy (file is locked)
|
| |
|
|
|
| |
Amoung other fixes, this means that addurl will stage added files even if
adding one of the urls fails.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
statfs(".", 0xffa8ad50) = -1 EOVERFLOW (Value too large for defined data type)
Ref <20141222221621.GO7251@onerussian.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
addurl behavior change: When downloading an url ending in .torrent,
it will download files from bittorrent, instead of the old behavior
of adding the torrent file to the repository.
Added Recommends on aria2 and bittornado | bittorrent.
This commit was sponsored by Asbjørn Sloth Tønnesen.
|
| |
|
|
| |
wget 1.16.
|
| |
|
|
| |
external special remote that handles magnet: and *.torrent urls.
|
| |
|
|
| |
getting the urls associated with a key.
|
| |
|
|
| |
Thanks, Jon Ander Peñalba.
|
| | |
|
| |
|
|
|
|
|
|
| |
Now that deps are sorted out in hackage, cabal is unlikely to try to
install a too old AWS, so I don't think this flag is worth the bother of
being completely correct with the dependency versioning.
This avoids me needing to enable to flag on the autobuilders..
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
Git/bin, since the latter is not in the default msysgit PATH.
|
| | |
| |
| |
| | |
includes it.
|
| | |
| |
| |
| | |
could be taken to read that's the only time git-annex runs gpg, which is not the case.
|
| | |
| |
| |
| |
| |
| | |
with annexed files.
Closes https://github.com/datalad/datalad/issues/18
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This commit was sponsored by Andrew Cant.
|
| |/ /
| |
| |
| | |
outside the menus.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This allows bypassing the direct mode guard in a safe way to do all sorts
of things including git revert, git mv, git checkout ...
This commit was sponsored by the WikiMedia Foundation.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
typechange staged in index
I had hoped that the git devs could change git's handling of partial
commits to not use a false index file, but seems not.
So, this relies on some git internals to detect that case. The test suite
has a test case added to catch it if changes to git break it.
This commit was sponsored by Paul Tagliamonte.
|
| | | |
|
Joey Hess
Joey Hess
Joey Hess