From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: 'sparse' clone idea
Date: Wed, 14 Jun 2006 10:23:54 +0200 [thread overview]
Message-ID: <e6oh2g$ngh$1@sea.gmane.org> (raw)
I wonder if 'sparse clone' idea described below would avoid the most
difficult part of 'shallow clone' idea, namely the [sometimes] need to
un-cauterize history. See: (<7vac8lidwi.fsf@assigned-by-dhcp.cox.net>).
'sparse clone' begins like 'shallow clone': full history is copied down to
specified point of history (cut-off or cauterization point for shallow
clone), but instead of cauterizing the history from that point downwards,
the history is simplified using grafts.
In the sparse part we need:
* all commits pointed by tags (if we clone/copy tags)
and other refs (if we clone/copy those tags)
* merge bases for all commits in full, and in the sparse part,
_including_ merge bases themselves
* all roots
Commits in sparse part would be connected like in original history, only
skipping "uniteresting" commits.
Thoughts? Comments?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next reply other threads:[~2006-06-14 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 8:23 Jakub Narebski [this message]
2006-06-14 9:20 ` 'sparse' clone idea Johannes Schindelin
2006-06-14 9:44 ` Jakub Narebski
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='e6oh2g$ngh$1@sea.gmane.org' \
--to=jnareb@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.