From: Joshua Jensen <jjensen@workspacewhiz•com>
To: weigelt@metux•de
Cc: git@vger•kernel.org
Subject: Re: Cutting history
Date: Fri, 09 Jul 2010 22:08:46 -0600 [thread overview]
Message-ID: <4C37F24E.30407@workspacewhiz.com> (raw)
In-Reply-To: <20100710032553.GB554@nibiru.local>
----- Original Message -----
From: Enrico Weigelt
Date: 7/9/2010 9:25 PM
> I'm using git for automatic backups (eg. database dumps). This
> works quite well, but as time goes, the history (and so the repo)
> gets larger and larger. It would be really nice to allow cutting
> off old stuff (eg. after N commits in the past).
>
> Maybe that could be done by introducing "stopper" tags: commits
> that have an stopper-tag may have missing parents, and git-gc
> can be told to ignore those parents and throw away everything
> behind the stopper (if not referenced otherwise).
>
> A probably cleaner, but more invasive way could be making refs
> to vectors, which may contain stop points (multiple ones in case
> of merges) additionally to the start point. Remote transmits only
> contain the commits within this range, and GC also just scans
> the range (instead of following all parents).
Your post reminded me of this: http://progit.org/2010/03/17/replace.html
Josh
next prev parent reply other threads:[~2010-07-10 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 3:25 Cutting history Enrico Weigelt
2010-07-10 4:08 ` Joshua Jensen [this message]
2010-07-10 6:43 ` Chris Frey
2010-07-10 8:47 ` Jakub Narebski
2010-07-10 10:40 ` Martin Pettersson
2010-07-10 11:58 ` Ævar Arnfjörð Bjarmason
2010-07-10 20:12 ` Ævar Arnfjörð Bjarmason
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=4C37F24E.30407@workspacewhiz.com \
--to=jjensen@workspacewhiz$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=weigelt@metux$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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