git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacob Helwig <jacob.helwig@gmail.com>
To: Larry D'Anna <larry@elder-gods.org>
Cc: Andrew Benton <b3nton@gmail.com>, git@vger.kernel.org
Subject: Re: Configuring git to for forget removed files
Date: Sun, 21 Feb 2010 13:14:02 -0800	[thread overview]
Message-ID: <20100221211402.GA1493@vfb-9.home> (raw)
In-Reply-To: <20100221203212.GA10876@cthulhu>

On 15:32 Sun 21 Feb     , Larry D'Anna wrote:
> * Andrew Benton (b3nton@gmail.com) [100220 05:37]:
> > Hello world
> > I have a project that I store in a git repository. It's a bunch of source tarballs and
> > some bash scripts to compile it all. Git makes it easy to distribute any changes I make
> > across the computers I run. The problem I have is that over time the repository gets ever
> > larger. When I update to a newer version of something I git rm the old tarball but git
> > still keeps a copy and the folder grows ever larger. At the moment the only solution I
> > have is to periodically rm -rf .git and start again. This works but is less than ideal
> > because I lose all the history for my build scripts.
> > What I would like is to be able to tell git to not keep a copy of anything that has been
> > git rm. The build scripts never get removed, only altered so their history would be
> > preserved. Is it possible to make git delete its backup copies of removed files?
> 
> This reminds me of a scenario I wish git had some way of supporting: I have a
> large collection of mp3s that I have duplicated across several computers.  I
> would love to be able to use git to sync changes between the copies, but there
> are several problems: 
> 
> 1) git is really slow when dealing with thousands of multi-megabyte blobs.
> 
> 2) commiting it to git is going to double the size of the directory, and I don't
> really have space for that on one of the computers that the directory lives on.
> 
> 3) there's no way to discard old history without breaking push and pull.
> 
> I'm not sure exactly what it would take to address 1, but 2 could be addressed
> pretty easily using btrfs file clones (once btrfs is stable), and 3 could be
> dealt with by improving support for shallow clones.
> 
>      --larry

In all seriousness: Why not use a tool that was actually designed for
what you're trying to do? (Sync a music collection across computers.)
Something like syrep[0]?

[0] http://0pointer.de/lennart/projects/syrep

-- 
Jacob Helwig

      reply	other threads:[~2010-02-21 21:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 10:37 Configuring git to for forget removed files Andrew Benton
2010-02-20 15:41 ` Tim Visher
2010-02-20 18:50 ` Avery Pennarun
2010-02-20 19:16 ` Junio C Hamano
2010-02-21  2:47 ` Jonathan Nieder
2010-02-21 13:32   ` Andrew Benton
2010-02-21 20:32 ` Larry D'Anna
2010-02-21 21:14   ` Jacob Helwig [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100221211402.GA1493@vfb-9.home \
    --to=jacob.helwig@gmail.com \
    --cc=b3nton@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=larry@elder-gods.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.
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 NNTP newsgroup(s).