From: Torsten Wagner <torsten.wagner@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Keeping org files under git - trimming the repository
Date: Wed, 5 Aug 2009 15:53:40 +0900 [thread overview]
Message-ID: <200908051553.40145.torsten.wagner@googlemail.com> (raw)
In-Reply-To: <BF2B7F9E-FAD4-4A29-AF1B-8FBB0E14AF00@alexanderonline.org>
Hi,
>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.
please define giant :)
compared to a plain copy of files under git.
Please consider that every commit create a small overhead to store a commit.
That means if you commit very small changes every minute or so... your git
might blow up.
Do you use any autosave function ? 1 one year saving (and commiting) every 15
min) means 35.000 commits if every auto-commit keeps the sentence "Auto-commit
from my org-files" :this creates 29 bytes * 35.000 commits which ends up to be
1 MB just for storing the log-file text. Other values and things will add to
this.
So please check how many commits you have already.
Repack and gc helps to clean up a bit of the overhead.
As for your concerns to make it smaller again. If you are not interested in
keeping the history of the files any more, most simply might be just create a
new git repro, copy the actual versions of the files to this repro and add them
to git.
Best regards
Totti
prev parent reply other threads:[~2009-08-05 6:53 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
2009-08-05 6:53 ` Torsten Wagner [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=200908051553.40145.torsten.wagner@googlemail.com \
--to=torsten.wagner@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).