From: Tyler Smith <tyler@plantarum.ca>
To: Brenda Butler <bjb@mojatatu.com>
Cc: Kyle Meyer <kyle@kyleam.com>, orgmode list <emacs-orgmode@gnu.org>
Subject: Re: org files and projects nested git repositories
Date: Thu, 31 Dec 2015 14:00:56 -0500 [thread overview]
Message-ID: <877fjul9xz.fsf@plantarum.ca> (raw)
In-Reply-To: <CAEj_wPQn6D5Erm1K6_LdwWWcgKmqZXCo6fBfJMvVCN2tYcJ2aQ@mail.gmail.com> (Brenda Butler's message of "Thu, 31 Dec 2015 13:53:52 -0500")
Brenda Butler <bjb@mojatatu.com> writes:
> I have tried links, but in all my attempts the links break whenever the
> source or the target is committed to version control. My understanding
> that each new commit to a file effectively changes the inode, breaking
> the link
>
> Sounds like you might be using hard links instead of symbolic links ...
> but first, are you using a unix-like system or another system? The symbolic link is a unix-like thing.
>
I'm on Debian, so links are available. I recall having to fix an issue
with Emacs' backup-files taking over the inodes. That was easily fixed
once I knew it was an issue. I don't recall the details, but it seemed
that the links still got garbled on commit. I'll take another look,
now that I know it should work.
Tyler
--
http://plantarum.ca
next prev parent reply other threads:[~2015-12-31 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 17:38 org files and projects nested git repositories Tyler Smith
2015-12-31 18:01 ` Ken Mankoff
2015-12-31 18:33 ` Tyler Smith
2015-12-31 18:42 ` Mike McLean
2016-01-01 10:02 ` Alan Schmitt
2016-01-01 12:33 ` Ken Mankoff
2016-01-04 13:04 ` Alan Schmitt
2015-12-31 18:20 ` Kyle Meyer
2015-12-31 18:38 ` Tyler Smith
2015-12-31 18:53 ` Brenda Butler
2015-12-31 19:00 ` Tyler Smith [this message]
2015-12-31 18:55 ` Kyle Meyer
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fjul9xz.fsf@plantarum.ca \
--to=tyler@plantarum.ca \
--cc=bjb@mojatatu.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).