From: Ben Alexander <firstname.lastname@example.org>
To: org-mode Mailinglist <email@example.com>
Subject: Keeping org files under git - trimming the repository
Date: Tue, 4 Aug 2009 15:10:19 +0300 [thread overview]
Message-ID: <BF2B7F9E-FAD4-4A29-AF1B-8FBB0E14AF00@alexanderonline.org> (raw)
This is really more of a git question, but I keep my org file stored
under git and I've seen other people on this list speak of doing the
same. Different people cite different benefits:
+ keeping home and work copies of todo.org in sync
+ storing todo.org on a USB stick for transport instead of using a
+ safety while editing. If a slip of the fingers hits C-k on a folded
line and you don't notice it for a long time, git allows you to find
when that happen (git blame) and 'cherry-pick' a patch to bring the
lost subtree forward in time.
I don't really know how to do any of these things in git, but that's
what you all say :-)
About a year ago, I decided to learn how to write "macros" in lisp and
started by teaching myself about the after-save-hook. I added a hook
to auto commit every time I saved any org file. My simple, small text
file of todo items is now a giant git repository.
At last a question or two: Does this happen to you? What do you do?
What new git command do I need to learn in order to do it?
Is there some way to clone my git repo onto my USB stick, but make it
a subset instead of the whole thing? That would be useful for me to
learn for other git projects!
(and thanks to you all for the interesting discussions and excellent
next reply other threads:[~2009-08-04 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 12:10 Ben Alexander [this message]
2009-08-04 12:26 ` Keeping org files under git - trimming the repository Benjamin Andresen
2009-08-04 13:31 ` Matt Lundin
2009-08-05 6:18 ` Ian Barton
2009-08-05 6:53 ` Torsten Wagner
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).