From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: [OT] Git plus Syncthing: breaking hard links
Date: Wed, 06 Apr 2016 14:41:10 +0800 [thread overview]
Message-ID: <87pou38cjd.fsf@ericabrahamsen.net> (raw)
In-Reply-To: ne1fl0$gd4$1@ger.gmane.org
Tim Howes <timhowes@berkeley.edu> writes:
> To avoid data loss, Syncthing creates a temporary file during transfer
> with the name ~syncthing~.{filename}.tmp
>
> If the transfer completes successfully, then it moves that file in place
> of the previous version. It's a new inode, not an update of the previous
> inode, so the hard link will be lost.
Ugh, that's what I was starting to suspect.
> Instead of using hard links, you could share your git repo folder
> directly using Syncthing, but use an .stignore file to exclude the files
> that you want to keep private (such as the .git directory).
Luckily you're right -- it isn't all that hard to work around. I'm
currently using one git repo to manage both my work-related *and*
personal Org files, and there's no particular reason to be doing that.
I'll split the repos, keep the work one in the Syncthing folder, and
sidestep the problem altogether.
Thanks to all who responded!
Eric
next prev parent reply other threads:[~2016-04-06 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 6:34 [OT] Git plus Syncthing: breaking hard links Eric Abrahamsen
2016-04-05 7:58 ` Eric S Fraga
2016-04-05 8:04 ` Eric Abrahamsen
2016-04-05 12:45 ` Nick Dokos
2016-04-05 23:29 ` briangpowell .
2016-04-05 22:53 ` Tim Howes
2016-04-06 6:41 ` Eric Abrahamsen [this message]
2016-04-06 23:38 ` Adam Porter
2016-04-06 23:47 ` Adam Porter
2016-04-07 0:48 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pou38cjd.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.