Commit graph

36776 commits

Author SHA1 Message Date
Joey Hess
8f297cb64f
remove old dead link 2020-04-01 15:44:15 -04:00
Joey Hess
acb356d75d
reorg more 2020-04-01 15:42:59 -04:00
Joey Hess
7d196c3e0d
move to right place and remove debian and hackage matrix embeds which have stopped working 2020-04-01 15:40:44 -04:00
Joey Hess
43d3948e52
added the datalad standalone build CI status badge 2020-04-01 15:38:40 -04:00
Joey Hess
9cb6c4b189
Merge branch 'master' of ssh://git-annex.branchable.com 2020-04-01 10:28:03 -04:00
xloem
ad483f5e23 2020-03-31 23:40:12 +00:00
thk
f4890ae642 2020-03-31 06:43:39 +00:00
thk
5df80188be Added a comment: Also problem with USB drives 2020-03-31 06:36:14 +00:00
yarikoptic
a180418843 Added a comment 2020-03-31 01:22:54 +00:00
https://openid.jorsn.eu/
8f1a988b43 Added a comment: automatic repository upgrades 2020-03-30 23:24:51 +00:00
https://openid.jorsn.eu/
5341fbc270 removed error 2020-03-30 22:41:59 +00:00
https://openid.jorsn.eu/
8eb4a82569 2020-03-30 22:41:17 +00:00
vinicius.vin@6d4d58c59c394cd744d469c9d7c41e264331dfcd
3f02d0f8ac Added a comment 2020-03-30 21:02:52 +00:00
Joey Hess
435c722904
remove unused import 2020-03-30 16:07:10 -04:00
Joey Hess
87d5583a91
use programPath consistently, not readProgramFile
Improve git-annex's ability to find the path to its program, especially
when it needs to run itself in another repo to upgrade it.

Some parts of the code used readProgramFile, probably because I forgot that
programPath exists.

I noticed this when a git-annex auto-upgrade failed because it was running
git-annex upgrade --autoonly, but the code to run git-annex used
readProgramFile, which happened to point to an older build of git-annex.
2020-03-30 16:06:27 -04:00
Joey Hess
f83ead0240
fix cleanup of old rpms 2020-03-30 15:17:25 -04:00
Joey Hess
fcdd6d0c53
sync with archive.org always 2020-03-30 15:13:16 -04:00
Joey Hess
9717915635
add news item for git-annex 8.20200330 2020-03-30 13:47:14 -04:00
Joey Hess
dbad6c5c39
releasing package git-annex version 8.20200330 2020-03-30 13:46:24 -04:00
Joey Hess
9cc1917295
close 2020-03-30 12:35:41 -04:00
yarikoptic
dd898afb40 Added a comment: Let's just close 2020-03-30 16:32:24 +00:00
Joey Hess
f6d19b18f6
remove unused imports 2020-03-30 12:11:52 -04:00
Joey Hess
0f6251ac6a
followup 2020-03-30 12:03:38 -04:00
Joey Hess
0e4d80d5c1
remove pre-commit hook
This was originally added so that unannex could prevent the hook from
running while files were in a state that the hook would interpret as
old-style unlocked and so would lock.

Now that's gone, so the only thing the hook was preventing was two
pre-commit processes running simulantaneously. But such concurrency
is normal in git-annex and should not be a problem.

Does mean that .git/hooks/pre-commit-annex might run more concurrently,
that seems the only risk of it causing any problems.
2020-03-30 11:54:04 -04:00
Joey Hess
1aabcd1038
moreinfo 2020-03-30 11:51:03 -04:00
Joey Hess
e6adfa1dc1
close per comments 2020-03-30 11:48:44 -04:00
Ilya_Shlyakhter
f7311ffc9d Added a comment: clarification re: upgrades 2020-03-30 15:24:01 +00:00
andrew
c29943f400 Added a comment: spotlight and macOS 2020-03-29 15:27:40 +00:00
erewhon
eec916a733 2020-03-28 17:52:28 +00:00
erewhon
89a056aed6 2020-03-28 16:47:27 +00:00
Soxofaan
ffafed4d82 Fix typo remotes.log -> remote.log 2020-03-28 13:36:45 +00:00
Soxofaan
63e75b71f8 removed duplicate "encryption=none" in initremote command 2020-03-28 10:41:53 +00:00
vinicius.vin@6d4d58c59c394cd744d469c9d7c41e264331dfcd
86bdda710f Added a comment 2020-03-27 23:04:34 +00:00
Ilya_Shlyakhter
fe8fa1a1e0 Added a comment 2020-03-27 21:12:18 +00:00
Ilya_Shlyakhter
2fd97e780b Added a comment 2020-03-27 21:11:14 +00:00
kyle
fd8a9a54e2 Added a comment: comment: resolved by 7.20191024 2020-03-27 20:49:44 +00:00
Ilya_Shlyakhter
de466ed0ad Added a comment: git add behavior 2020-03-27 20:49:19 +00:00
vinicius.vin@6d4d58c59c394cd744d469c9d7c41e264331dfcd
4cf46f56e2 2020-03-27 20:23:15 +00:00
vinicius.vin@6d4d58c59c394cd744d469c9d7c41e264331dfcd
0784136c3c 2020-03-27 20:19:10 +00:00
j@833cff95824930f20b36c340f1217182b6937407
d2621209a9 2020-03-27 12:30:44 +00:00
kyle
dfee97cd56 Added a comment 2020-03-26 23:32:56 +00:00
lykos@d125a37d89b1cfac20829f12911656c40cb70018
d27a94eec0 Added a comment 2020-03-26 20:36:28 +00:00
Joey Hess
c9ac7aa338
patch applied 2020-03-26 15:18:47 -04:00
Kyle Meyer
376e69ec65
adjust: Propagate submodule changes back to original branch
When the recorded submodule commit changes on an adjusted branch, the
change is carried in the function that reverseAdjustedCommit passes
for adjustTree's adjusttreeitem parameter.  Update the CommitObject
handling in adjustTree to consider adjusttreeitem so that a submodule
change is synced back.
2020-03-26 15:16:08 -04:00
Joey Hess
78977ce417
correct inaccurate part of comment 2020-03-26 15:08:12 -04:00
Joey Hess
42d73a3e62
comment 2020-03-26 14:48:54 -04:00
Joey Hess
173465592f
changelog for Kyle's other fix, and close bug 2020-03-26 13:18:41 -04:00
Kyle Meyer
39131b55ca
add --force-small: Send all non-regular files through addFile
Running `git annex add --force-small` on a modified submodule fails
when the submodule path is fed to hash-object.  This failure is
unlikely to be triggered by a caller passing a submodule explicitly to
`git annex add` because there's nothing useful that annex-add can do
with a submodule.  A more likely scenario for hitting this failure is
that the caller passes "." or a subdirectory to `annex-add` while a
submodule underneath the specified path happens to be modified.

addSmallOverridden already routes symbolic links through addFile
rather than using the custom hash-object/update-index call.  The
latter is valid only for regular files, so extend this condition so
that everything that isn't a regular file goes through addFile.  Doing
so avoids the above error because submodules come in as directories.
2020-03-26 13:14:16 -04:00
Joey Hess
c0ceb969e6
changelog for Kyle's fix 2020-03-26 13:12:49 -04:00
Kyle Meyer
339aebc6ad
add --force-small: Don't dereference link when checking file status
addSmallOverridden calls getFileStatus and then checks the result with
isSymbolicLink.  getFileStatus dereferences symbolic links, so
isSymbolicLink will always return false (assuming the getFileStatus
call doesn't fail on a broken link).  Use getSymbolicLinkStatus
instead.
2020-03-26 13:11:27 -04:00