From: Junio C Hamano <gitster@pobox.com>
To: Sam Vilain <sam@vilain.net>
Cc: Joshua Roys <roysjosh@gmail.com>,
gittorrent@lists.utsl.gen.nz, git@vger.kernel.org,
Jonas Fonseca <fonseca@diku.dk>
Subject: Re: GTP/0.1 terminology 101: commit reels and references
Date: Mon, 28 Jul 2008 00:24:12 -0700 [thread overview]
Message-ID: <7vk5f6tqsj.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1217228570.6750.24.camel@maia.lan> (Sam Vilain's message of "Mon, 28 Jul 2008 19:02:50 +1200")
Sam Vilain <sam@vilain.net> writes:
>> Commit reels can also, and generally do, include the objects required
>> for a specific commit.
>
> Yes. The only times where they wouldn't contain all the objects
> required for the commits within the reel, is when those objects happened
> to be contained by a previous reel.
What do you mean by "previous" reel? It is not quite defined in your
message but perhaps defined elsewhere?
How is this different from a bundle? Does a reel, unlike a bundle,
contain the full tree for the bottom commits?
> This is one of the design decisions which I think may be a mistake; a
> less expensive to calculate definition of a reel would be *all* objects
> between the starting and ending Reference objects.
Do you mean all such objects and nothing else? That would imply that a
reel is quite similar to a bundle (but neither rev-list --objects-edge
nor bundle guarantees that the result is minimal).
next prev parent reply other threads:[~2008-07-28 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <488D42B6.4030701@gmail.com>
2008-07-28 7:02 ` GTP/0.1 terminology 101: commit reels and references Sam Vilain
2008-07-28 7:24 ` Junio C Hamano [this message]
2008-07-28 10:03 ` Sam Vilain
2008-07-28 12:01 ` Johannes Schindelin
2008-07-28 19:26 ` Sam Vilain
2008-07-28 22:30 ` Johannes Schindelin
2008-07-29 7:00 ` Sam Vilain
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=7vk5f6tqsj.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=fonseca@diku.dk \
--cc=git@vger.kernel.org \
--cc=gittorrent@lists.utsl.gen.nz \
--cc=roysjosh@gmail.com \
--cc=sam@vilain.net \
/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