{"thread":{"id":"6945","subject":"Centralized repository","startedAt":"2007-02-25T02:14:27Z","lastAt":"2007-02-25T21:08:34Z","messageCount":5,"participants":["bob","Jeff King","Andy Parkins","Robin Rosenberg","Martin Waitz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"35413","messageId":"EF7846A2-C573-4018-B399-EBBEEE2812A4@mac.com","threadId":"6945","inReplyTo":null,"subject":"Centralized repository","fromName":"bob","fromEmail":"kranki@mac.com","sentAt":"2007-02-25T02:14:27Z","receivedAt":"2007-02-25T02:14:27Z","isPatch":false,"sender":{"key":"kranki@mac.com","avatar":null},"body":"I know that this has been mentioned before.  So, I will only bring it  \nup once (from me at least).\n\nI have a project that is currently over 2gigs without .git and  \ngrowing.  It is a personal website that I use to provide/remind me of  \nthings that I used to remember when I was younger.  When you put a  \nGIT repostitory in it, you get almost 4gigs of space taken (and this  \namount is growing all the time).  Then I keep it centralized, because  \nI own several machines (OK, way too many, over 20 currently,  \ndedicated to Folding@Home).  So, it takes up a lot of disk space over  \nall those machines.\n\nBecause it is so big, cloning no longer works.  I can't remember the  \nexact errors, but I gave up and now tar up  a semi-current version  \nand untar it on a new/re-installed machine.  Then I do a \"pull\" to  \nupdate it and that works when the clone doesn't.  I should mention  \nthat I have only 2 windows machines, but run GIT on all the rest  \nwhich are Linux and MacOSX machines.\n\nAnyway, for this one repository, I would really like GIT to support  \nthe CVS/SVN central repository system.  The rest of the time, I am  \nquite happy with GIT's distributed system even though all of my  \nrepositories are really just for me.\n\nLast, thanks for GIT.  I really enjoy it and use it daily and have  \nnever had it fail on me (no matter what I did!)!\n\nBob White\n"},{"id":"35415","messageId":"20070225060400.GB17031@coredump.intra.peff.net","threadId":"6945","inReplyTo":"EF7846A2-C573-4018-B399-EBBEEE2812A4@mac.com","subject":"Re: Centralized repository","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2007-02-25T06:04:00Z","receivedAt":"2007-02-25T06:04:00Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Feb 24, 2007 at 09:14:27PM -0500, bob wrote:\n\n> Anyway, for this one repository, I would really like GIT to support  \n> the CVS/SVN central repository system.  The rest of the time, I am  \n> quite happy with GIT's distributed system even though all of my  \n> repositories are really just for me.\n\nFor a while I was running git with an 80-gig repository of media files.\nI found it useful to network mount the central git repo (I used SMB),\nand clone to the local machine using alternates (i.e., \"git clone -s\n/net/mounted/git /local/git\").  It should work as a normal git repo,\nexcept that all object accesses will transparently go over the network,\nwhich obviously slows things down a bit (but no slower than CVS!).\n\nYou should be able to pack at your size of repo (I obviously couldn't,\nbut I was working with a few very large files, so the overhead wasn't\ntoo bad).\n\nHTH,\n-Peff\n"},{"id":"35428","messageId":"200702250951.37867.andyparkins@gmail.com","threadId":"6945","inReplyTo":"EF7846A2-C573-4018-B399-EBBEEE2812A4@mac.com","subject":"Re: Centralized repository","fromName":"Andy Parkins","fromEmail":"andyparkins@gmail.com","sentAt":"2007-02-25T09:51:34Z","receivedAt":"2007-02-25T09:51:34Z","isPatch":false,"sender":{"key":"andyparkins@gmail.com","avatar":null},"body":"On Sunday 2007, February 25, bob wrote:\n\n> Anyway, for this one repository, I would really like GIT to support\n> the CVS/SVN central repository system.  The rest of the time, I am\n\nIn the case of subversion: you really /wouldn't/ want that model.  \nSubversion keeps a local pristine copy in the .svn directory of every \nfile.  This makes local diffs and stats fast and not require network \naccess, but also doubles the storage requirements of your working \ndirectory.\n\nI've found that a packed git repository is often smaller than a full \ncheckout of the project (it's almost scary actually - your entire \nproject's history in less space than the project).\n\n\nAndy\n-- \nDr Andrew Parkins, M Eng (Hons), AMIEE\nandyparkins@gmail.com\n"},{"id":"35435","messageId":"200702251650.13381.robin.rosenberg.lists@dewire.com","threadId":"6945","inReplyTo":"200702250951.37867.andyparkins@gmail.com","subject":"Re: Centralized repository","fromName":"Robin Rosenberg","fromEmail":"robin.rosenberg.lists@dewire.com","sentAt":"2007-02-25T15:50:11Z","receivedAt":"2007-02-25T15:50:11Z","isPatch":false,"sender":{"key":"robin.rosenberg@dewire.com","avatar":"https://avatars.githubusercontent.com/u/46357?v=4"},"body":"söndag 25 februari 2007 10:51 skrev Andy Parkins:\n> On Sunday 2007, February 25, bob wrote:\n> \n> > Anyway, for this one repository, I would really like GIT to support\n> > the CVS/SVN central repository system.  The rest of the time, I am\n> \n> In the case of subversion: you really /wouldn't/ want that model.  \n> Subversion keeps a local pristine copy in the .svn directory of every \n> file.  This makes local diffs and stats fast and not require network \n> access, but also doubles the storage requirements of your working \n> directory.\n> \n> I've found that a packed git repository is often smaller than a full \n> checkout of the project (it's almost scary actually - your entire \n> project's history in less space than the project).\n\nThat doesn't apply to a repo full of (already compressed) binaries media \nfiles. You cannot pack them unless the binaries are so small  that the wasted \nspace at the end of the last disk block is a significant amount of the total \nused. You cannot diff them either, other than seeing that they are different. \n\nBesides the 4 GB mentioned isn't much nowadays. If it is annoying to have \nthe .git directory in the same filesystem tree you can place the .git \ndirectory somewhere else and drop a  symbolic link in it's place. \n\nBtw, is it possible to make a full repo shallow again, by pruning  \nthe \"uninteresting\" part of the history? That would make it possible to trim \ndown the size of the local archive. \n\n-- robin\n"},{"id":"35455","messageId":"20070225210834.GQ21842@admingilde.org","threadId":"6945","inReplyTo":"EF7846A2-C573-4018-B399-EBBEEE2812A4@mac.com","subject":"Re: Centralized repository","fromName":"Martin Waitz","fromEmail":"tali@admingilde.org","sentAt":"2007-02-25T21:08:34Z","receivedAt":"2007-02-25T21:08:34Z","isPatch":false,"sender":{"key":"tali@admingilde.org","avatar":"https://gravatar.com/avatar/3f89b03eee362187effabe257898735b475673a12265c398ea9161259ae91553?d=mp&s=160"},"body":"hoi :)\n\nOn Sat, Feb 24, 2007 at 09:14:27PM -0500, bob wrote:\n> Because it is so big, cloning no longer works.  I can't remember the  \n> exact errors, but I gave up and now tar up  a semi-current version  \n> and untar it on a new/re-installed machine.  Then I do a \"pull\" to  \n> update it and that works when the clone doesn't.\n\nthis is fixed in the master branch now.\n\n-- \nMartin Waitz\n"}]}