On Tue, Sep 09, 2014 at 05:48:52PM +0200, martin f krafft wrote:
> also sprach Joey Hess [2014-09-09 17:20 +0200]:
> Unfortunately, the requirement for the remote to already exist kinda makes it
> hard to use, for two reasons:
>
> 1. The location depends on both sides of the equation, there's no
martin f krafft wrote:
> 2. I'd want to set up the special remote once locally, and then
> use it elsewhere. If I have to set it up elsewhere, I might
> just as well add the remote directly…
>
> % git annex initremote one type=git location=`pwd`
> (merging origin/git-annex in
also sprach Joey Hess [2014-09-09 17:20 +0200]:
> Note that the part after the -- here is just a description, and can be
> any free-form text.
I was going to suggest that there could be another field added to
the protocol, but…
> Recent versions of git-annex have a hidden feature that's used by
martin f krafft wrote:
> 296d71bb-1aef-4381-b15a-8c9f13836254 --
> madduck@albatross:~/family/veronika/photos
Note that the part after the -- here is just a description, and can be
any free-form text. Even if it's kept at the default which happens to
have the same form as a git ssh remote url,
also sprach Adam Spiers [2014-09-09 15:59 +0200]:
> This is how I do it:
>
> http://lists.madduck.net/pipermail/vcs-home/2012-May/000806.html
Right, so you seem to have a central mr config repo with all the
knowledge of who has which repo checked out, so that you can then
say that repo XYZ shoul
On 9 September 2014 14:24, martin f krafft wrote:
> Has anyone come up with a smart way of auto-configuring
> relationships between hosts? git-annex keeps track of where files
> are, so theoretically, it should be able to auto-configure the
> remotes if I tell it that two remotes are directly in r