Re: org files and projects nested git repositories

[Tyler Smith <tyler@plantarum.ca>]

Kyle Meyer <kyle@kyleam.com> writes:
>
> In addition to what Ken suggested, another option is to use links to
> populate the agenda directory.  Have a git repo for your Org notes and
> agenda file (your "org" directory above), and add this directory (or one
> of its subdirectories) to org-agenda-files so that all the Org files in
> that directory are considered agenda files.
>
> Keep project-related Org files in the given project directory (as you do
> above), and create a symbolic link for the Org file in the agenda
> directory.  The project directory will then track the content of the Org
> file, and the agenda repo will just track the presence of the link.
>

Thanks Kyle.

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. 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.

Best,

Tyler

-- 
http://plantarum.ca