summaryrefslogtreecommitdiff
path: root/doc/tips
Commit message (Collapse)AuthorAge
* (no commit message)Gravatar memeplex2017-04-14
|
* (no commit message)Gravatar memeplex2017-04-14
|
* Added remote.<name>.annex-push and remote.<name>.annex-pullGravatar Joey Hess2017-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The former can be useful to make remotes that don't get fully synced with local changes, which comes up in a lot of situations. The latter was mostly added for symmetry, but could be useful (though less likely to be). Implementing `remote.<name>.annex-pull` was a bit tricky, as there's no one place where git-annex pulls/fetches from remotes. I audited all instances of "fetch" and "pull". A few cases were left not checking this config: * Git.Repair can try to pull missing refs from a remote, and if the local repo is corrupted, that seems a reasonable thing to do even though the config would normally prevent it. * Assistant.WebApp.Gpg and Remote.Gcrypt and Remote.Git do fetches as part of the setup process of a remote. The config would probably not be set then, and having the setup fail seems worse than honoring it if it is already set. I have not prevented all the code that does a "merge" from merging branches from remotes with remote.<name>.annex-pull=false. That could perhaps be done, but it would need a way to map from branch name to remote name, and the way refspecs work makes that hard to get really correct. So if the user fetches manually, the git-annex branch will get merged, for example. Anther way of looking at/justifying this is that the setting is called "annex-pull", not "annex-merge". This commit was supported by the NSF-funded DataLad project.
* commentGravatar Joey Hess2017-04-05
|
* commentGravatar Joey Hess2017-04-05
|
* Added a comment: onion-graterGravatar anarcat2017-03-30
|
* Added a comment: autostart and foreground together doesn't seem to workGravatar oberix@c7a19cddb1663df0c612a979b9d13b0d67f1f69a2017-03-30
|
* add annex-sync setting sampleGravatar anarcat2017-03-27
|
* link to torrent pageGravatar anarcat2017-03-27
|
* some issue i have come up with a few times and workaroundsGravatar anarcat2017-03-27
|
* Added a comment: Tracking GUIDsGravatar ewen2017-03-21
|
* Add note about tracking guids since 2015Gravatar ewen2017-03-21
|
* commentGravatar Joey Hess2017-03-21
|
* Added a comment: Track GUIDs to avoid duplicate downloadsGravatar ewen2017-03-21
|
* removedGravatar ewen2017-03-21
|
* Added a comment: Track GUIDs to avoid duplicate downloadsGravatar ewen2017-03-21
|
* Added a comment: Beware global configurations!Gravatar joern.mankiewicz@06fb5bc9b732f143dee3606866362f562531310d2017-03-20
|
* commentGravatar Joey Hess2017-03-20
|
* responseGravatar Joey Hess2017-03-20
|
* Added a comment: Git-annex ignores annex.largefiles in .gitattributesGravatar joern.mankiewicz@06fb5bc9b732f143dee3606866362f562531310d2017-03-20
|
* commentGravatar Joey Hess2017-03-14
|
* Added a comment: Isn't this procedure assuming that lost+found contains only ↵Gravatar https://launchpad.net/~stephane-gourichon-lpad2017-03-14
| | | | uncorrupted previously annexed files?
* commentGravatar Joey Hess2017-03-03
|
* removedGravatar xloem2017-03-03
|
* Added a comment: Non-conforming blobsGravatar xloem2017-03-03
|
* Added a comment: Non-conforming blobsGravatar xloem2017-03-03
|
* clarificationGravatar Joey Hess2017-03-02
|
* Added a comment: Security of P2P repo is unclearGravatar dvicory2017-02-28
|
* better headingsGravatar Joey Hess2017-02-27
|
* larger headingsGravatar Joey Hess2017-02-27
|
* inheritable annex.securehashesonlyGravatar Joey Hess2017-02-27
| | | | | | | | | | | | | | | * init: When annex.securehashesonly has been set with git-annex config, copy that value to the annex.securehashesonly git config. * config --set: As well as setting value in git-annex branch, set local gitconfig. This is needed especially for annex.securehashesonly, which is read only from local gitconfig and not the git-annex branch. doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn has the rationalle for doing it this way. There's no perfect solution; this seems to be the least-bad one. This commit was supported by the NSF-funded DataLad project.
* make fsck check annex.securehashesonly, and new tip for working around SHA1 ↵Gravatar Joey Hess2017-02-27
| | | | | | collisions with git-annex This commit was sponsored by andrea rota.
* linkifyGravatar Joey Hess2017-02-17
|
* documentation updates for new receive.denyCurrentBranch=updateInstead supportGravatar Joey Hess2017-02-17
| | | | This commit was sponsored by andrea rota.
* correct spelling mistakesGravatar Edward Betts2017-02-12
|
* (no commit message)Gravatar git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c002017-01-31
|
* reusing repository uuid cannot result in data loss AFAIKGravatar Joey Hess2017-01-30
| | | | | | | | | | | | | | | | | | | Avoiding such problems is one reason why git-annex does active verification of other copies of a file when dropping. You could argue that reusing the uuid of a trusted repository leads to data loss, but that data loss doesn't really involve reusing the uuid, but instead is caused by deleting a trusted repository. Using trusted repositories without a great deal of care is a good way to blow off your foot, of which deleting them is only the most obvious; added some sections about that. If reusing a repository uuid could result in data loss then I'd be on board with making reinit run a fast fsck to update the location log, but since it can't, I feel that is not worth forcing. Not a bad idea to run fsck afterwards. Updated language about that. This commit was sponsored by Jake Vosloo on Patreon.
* Fixes ToCGravatar justin@561b4852d5c1d8db31dc571612954bde7bb325a12017-01-17
|
* backwards links againGravatar https://anarc.at/openid/2017-01-17
|
* fix linkGravatar https://anarc.at/openid/2017-01-17
|
* Page flow and antipattern separationGravatar justin@561b4852d5c1d8db31dc571612954bde7bb325a12017-01-17
|
* note an improvement on the reinit manpageGravatar https://anarc.at/openid/2017-01-17
|
* a list of problems i had with git-annexGravatar https://anarc.at/openid/2017-01-17
|
* fix link and clarifyGravatar Joey Hess2016-12-28
|
* add back share_with_a_friend_walkthrough, adapted for tor pairingGravatar Joey Hess2016-12-24
| | | | and some other xmpp to tor related changes
* enable-tor: When run as a regular user, test a connection back to the hidden ↵Gravatar Joey Hess2016-12-24
| | | | | | | | | | | | | | | | | | | service over tor. This way we know that after enable-tor, the tor hidden service is fully published and working, and so there should be no problems with it at pairing time. It has to start up its own temporary listener on the hidden service. It would be nice to have it start the remotedaemon running, so that extra step is not needed afterwards. But, there may already be a remotedaemon running, in communication with the assistant and we don't want to start another one. I thought about trying to HUP any running remotedaemon, but Windows does not make it easy to do that. In any case, having the user start the remotedaemon themselves lets them know it needs to be running to serve the hidden service. This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
* enable-tor: No longer needs to be run as root.Gravatar Joey Hess2016-12-20
| | | | | | When run by not root, su's to root automatically. This commit was sponsored by Brock Spratlen on Patreon.
* section on safe pairing code exchangeGravatar Joey Hess2016-12-19
|
* p2p --pair with magic wormhole (untested)Gravatar Joey Hess2016-12-18
| | | | | | It builds. I have not tried to run it yet. :) This commit was sponsored by Jake Vosloo on Patreon.
* Revert "p2p --link now defaults to setting up a bi-directional link"Gravatar Joey Hess2016-12-16
| | | | | | | | This reverts commit 6aa7e136b5d246228723f4c9996bda11f66c4445. On second thought, this was an overcomplication of what should be the lowest-level primitive. Let's build bi-directional links at the pairing level with eg magic wormhole.
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-01 16:04:49 +0000