From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Any idea why the git repo is so huge
Date: Tue, 02 Feb 2010 11:09:56 +0000 [thread overview]
Message-ID: <87fx5j3ncr.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <m0636gdn96.fsf@cam.ac.uk>
At Tue, 02 Feb 2010 09:01:57 +0000,
Leo wrote:
>
> Hello,
>
> The git repo I just checked out a minute ago is 54M, 20 times bigger
> than the org lisp files. Any idea why it is so large? Thanks.
ummm because there is a great deal of active development? Each change
requires an entry in the repository with the changes that entry was
responsible for.
next prev parent reply other threads:[~2010-02-02 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 9:01 Any idea why the git repo is so huge Leo
2010-02-02 11:09 ` Eric S Fraga [this message]
2010-02-02 12:29 ` Ian Barton
2010-02-02 16:12 ` Leo
2010-02-02 17:57 ` Richard Riley
2010-02-03 15:52 ` Christopher Allan Webber
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=87fx5j3ncr.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=sdl.web@gmail.com \
/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).