On Wed, Jul 24, 2013 at 5:33 AM, Philip Oakley <philipoakley@xxxxxxx> wrote: > In some sense a project with a sub-module is a narrow clone, split at a > 'commit' object. Yes, except narrow clone is more flexible. You have to decide the split boundary at commit time for sub-module, while you decide the same at clone time for narrow clone. > There have been comments on the git-user list about the > problem of accidental adding of large files which then make the repo's foot > print pretty large as one use case [Git is consuming very much RAM]. The > bigFileThreshold being one way of spotting such files as separate objects, > and 'trimming' them. I think rewriting history to remove those accidents is better than working around it (the same for accidentally committing password). We might be able to spot problems early, maybe warn user at commit time that they have added an exceptionally large blob, maybe before push time.. The "Git is consuming very much RAM" part is not right. We try to keep memory usage under a limit regardless of the size of a blob. There may be some cases we haven't fixed yet. Reports are welcome. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html