emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Tyler Smith <tyler@plantarum.ca>
Cc: orgmode list <emacs-orgmode@gnu.org>
Subject: Re: org files and projects nested git repositories
Date: Thu, 31 Dec 2015 13:55:42 -0500	[thread overview]
Message-ID: <87twmy78i9.fsf@kyleam.com> (raw)
In-Reply-To: <87bn96layw.fsf@plantarum.ca> (Tyler Smith's message of "Thu, 31 Dec 2015 13:38:47 -0500")

Tyler Smith <tyler@plantarum.ca> 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.

Are you thinking of hard links rather than symbolic links?  Symbolic
links should play well with Git (ignoring Windows).  The popular tool
git-annex is even built around symbolic links.

> In your use, are the targets and their links both under
> version control? If so, obviously they aren't breaking, so I must be
> doing something wrong when I try the same thing.

Yes, the target is under version control in the project repo, and the
agenda repo tracks a symbolic link to the target, so the content of that
file is just a path to the target.

--
Kyle

      parent reply	other threads:[~2015-12-31 18:55 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
2015-12-31 18:55     ` Kyle Meyer [this message]

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=87twmy78i9.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tyler@plantarum.ca \
    /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).