From: Ian Barton <firstname.lastname@example.org>
Cc: org-mode Mailinglist <email@example.com>
Subject: Re: Keeping org files under git - trimming the repository
Date: Wed, 05 Aug 2009 07:18:41 +0100 [thread overview]
Message-ID: <4A792441.firstname.lastname@example.org> (raw)
> 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!
I am not a git expert, but I think there a couple of things you can do:
Create a new branch and push just the branch to your usb stick.
Use git rebase to rewrite all your earlier commits into one huge commit.
Using rebase is a bit like juggling chain saws while walking blindfold
along a tightrope, so make sure that you pratice on a backup first.
next prev parent reply other threads:[~2009-08-05 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 12:10 Keeping org files under git - trimming the repository Ben Alexander
2009-08-04 12:26 ` Benjamin Andresen
2009-08-04 13:31 ` Matt Lundin
2009-08-05 6:18 ` Ian Barton [this message]
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).