From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Javier Domingo <javierdo1@gmail.com>
Cc: jaseem abid <jaseemabid@gmail.com>, git@vger.kernel.org
Subject: Re: Centralized git
Date: Tue, 31 Jul 2012 16:52:51 +0200 [thread overview]
Message-ID: <CACBZZX7drB62ohpPOEs03SGe12sDmGzJDcGMboF50y9QLa6HbA@mail.gmail.com> (raw)
In-Reply-To: <CALZVapm-=HXdfb6LCrc60HgUJA0ptzb+E5r3Y1C2w_0eBo1onQ@mail.gmail.com>
On Tue, Jul 31, 2012 at 3:08 PM, Javier Domingo <javierdo1@gmail.com> wrote:
> Network, in this case is cheaper. The thing is that If I commit
> frecuently, will have plenty of GBs of history, that nearly for sure I
> won't use. I just need to have other people's work to merge. But I
> want to think in Git style, I am pretty accustomed to that way of
> doing things. That is why I sent this mail here.
>
> The idea is that if I modify 700MBs of video, with 20 commits I would
> get in 21GB. And making a pull would be... just even more horrible
> than anything. That is why I need to have also last checkouts filter.
> Just download branch's HEADs.
You're obviously aware of git-annex, is there any reason you can't
just use that?
That would give you what you want, you'd have a moving window of
current files, and then you'd delete old files as they become
un-needed.
next prev parent reply other threads:[~2012-07-31 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALZVapnwGK=cKdHbZRsN0Ust7TAvFqa3AmYD7pzgoxdDxQh+uw@mail.gmail.com>
2012-07-31 12:03 ` Centralized git Javier Domingo
2012-07-31 12:55 ` jaseem abid
[not found] ` <CALZVapniy5iNJbuOikZdgHv2qQ80nDSATw8udV=Tk2wNgxXY4w@mail.gmail.com>
2012-07-31 13:08 ` Javier Domingo
2012-07-31 14:52 ` Ævar Arnfjörð Bjarmason [this message]
2012-07-31 15:47 ` Vipul Amler
2012-07-31 15:40 ` Edward Toroshchin
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=CACBZZX7drB62ohpPOEs03SGe12sDmGzJDcGMboF50y9QLa6HbA@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jaseemabid@gmail.com \
--cc=javierdo1@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.
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).