emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "John Wiegley" <johnw@newartisans.com>
To: emacs-orgmode@gnu.org
Cc: Joey Hess <joey@kitenet.net>
Subject: Using git-annex with org-attach
Date: Sat, 20 Oct 2012 07:59:09 -0700	[thread overview]
Message-ID: <m2wqylvuhe.fsf@newartisans.com> (raw)

I pushed a change to master that allows you to use the wonderful git-annex
utility[1] seamlessly with org-attach.  The way it works is as follows:

 1. If your `org-attach-directory' is a git working tree,

 2. and if you have run "git annex init" there,

 3. and if `org-attach-git-annex-cutoff' is non-nil and smaller than the size
    of the file you're attaching,

 4. then org-attach will "git annex add" the file; otherwise it will "git add"
    it.  (See the documentation for git-annex to discover exactly what this
    distinction means; basically it's the difference between "stored in Git
    forever", and "check-summed and tracked until I decide I don't need it on
    this machine anymore").

 5. You will have to run "git annex sync" yourself afterwards, or use the "git
    annex assistant" to keep your attachments automagically in sync with all
    your machines whenever they are reachable.

The value of git-annex is that it lets you associate truly huge files with a
Git repository that are check-summed and easily archived, which you can then
drop from your local attachments directory when you no longer need the file
there.  Later, if you need files that you dropped, use `C-c C-a F' and `M-!
git annex get . RET' to re-download those attachments back into your local
repo.

John

Footnotes: 
[1]  http://git-annex.branchable.com/

next             reply	other threads:[~2012-10-20 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20 14:59 John Wiegley [this message]
2012-10-22  9:43 ` tnx (was: Re: Using git-annex with org-attach) Giovanni Ridolfi
2012-10-22 21:31 ` Using git-annex with org-attach John Wiegley
2012-10-24 14:06 ` Bastien

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=m2wqylvuhe.fsf@newartisans.com \
    --to=johnw@newartisans.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=joey@kitenet.net \
    /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

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