From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Stefan Beller <sbeller@google.com>,
Shawn Pearce <spearce@spearce.org>, git <git@vger.kernel.org>
Subject: Re: RFC: Resumable clone based on hybrid "smart" and "dumb" HTTP
Date: Wed, 10 Feb 2016 13:07:43 -0800 [thread overview]
Message-ID: <xmqqd1s4z334.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160210210115.GA10155@google.com> (Jonathan Nieder's message of "Wed, 10 Feb 2016 13:01:15 -0800")
Jonathan Nieder <jrnieder@gmail.com> writes:
> --strict + --check-self-contained-and-connected check that the pack
> is self-contained. In the process they mark each object that is
> reachable from another object in the pack with FLAG_LINK.
>
> The objects not marked with FLAG_LINK are the roots.
Ahh, OK, if we already have the code that does it, I have no
objection. At some point before finalizing the pack on the disk we
would want to run fsck on all objects anyway, so having to pass
"--strict" to find objects that lack FLAG_LINK does not sound too
big a downside.
Thanks.
next prev parent reply other threads:[~2016-02-10 21:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 18:59 RFC: Resumable clone based on hybrid "smart" and "dumb" HTTP Shawn Pearce
2016-02-10 20:11 ` Shawn Pearce
2016-02-10 20:23 ` Stefan Beller
2016-02-10 20:57 ` Junio C Hamano
2016-02-10 21:22 ` Jonathan Nieder
2016-02-10 22:03 ` Jeff King
2016-02-10 21:01 ` Jonathan Nieder
2016-02-10 21:07 ` Junio C Hamano [this message]
2016-02-11 3:43 ` Junio C Hamano
2016-02-11 18:04 ` Shawn Pearce
2016-02-11 23:53 ` Duy Nguyen
2016-02-13 5:07 ` Junio C Hamano
2016-02-10 21:49 ` Jeff King
2016-02-10 22:17 ` Jonathan Nieder
2016-02-10 23:03 ` Jeff King
2016-02-10 22:40 ` Junio C Hamano
2016-02-11 21:32 ` Junio C Hamano
2016-02-11 21:46 ` Jeff King
2016-02-13 1:40 ` Blake Burkhart
2016-02-13 17:00 ` Jeff King
2016-02-14 2:14 ` Shawn Pearce
2016-02-14 17:05 ` Jeff King
2016-02-14 17:56 ` Shawn Pearce
2016-02-16 18:34 ` Stefan Beller
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=xmqqd1s4z334.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=sbeller@google.com \
--cc=spearce@spearce.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).