From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Subject: Truncating history (Re: Sparse clones)
Date: Fri, 13 Aug 2010 14:19:54 -0500 [thread overview]
Message-ID: <20100813191954.GA2003@burratino> (raw)
In-Reply-To: <20100813173147.GB27540@nibiru.local>
Hi,
Enrico Weigelt wrote:
> Fake-roots are special refs that declare certain commit objects
> as root-commits). Each time git walks down the history, it checks
> whether the current commit is an fake-root and so treats it as
> having no ancestor. That should be generic enough let everything
> else (commit, push, gc, etc) work as usual.
>
> The only tricky point is when to update remote fake-roots: the
> remote should not cut off my local repo (unless explicitly asked).
> So remote fake-roots should only be imported if the local/receiving
> side has not the dropped commits anymore.
You may be interested in grafts and replacement refs; see
git-filter-branch(1) and git-replace(1) for some hints.
Good luck,
Jonathan
prev parent reply other threads:[~2010-08-13 19:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 0:13 Sparse clones (Was: Re: [PATCH 1/2] upload-pack: support subtree packing) Elijah Newren
2010-07-28 1:05 ` Avery Pennarun
2010-07-28 3:06 ` Nguyen Thai Ngoc Duy
2010-07-28 3:38 ` Nguyen Thai Ngoc Duy
2010-07-28 3:58 ` Avery Pennarun
2010-07-28 6:12 ` Sverre Rabbelier
2010-07-28 7:59 ` Nguyen Thai Ngoc Duy
2010-07-28 14:48 ` Sverre Rabbelier
2010-07-28 7:11 ` Nguyen Thai Ngoc Duy
2010-07-28 3:31 ` Elijah Newren
2010-07-31 22:36 ` Elijah Newren
2010-07-28 3:36 ` Nguyen Thai Ngoc Duy
2010-07-28 3:59 ` Elijah Newren
2010-07-29 10:29 ` Nguyen Thai Ngoc Duy
2010-08-13 17:31 ` Enrico Weigelt
2010-08-13 19:19 ` Jonathan Nieder [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100813191954.GA2003@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).