From: Duy Nguyen <pclouds@gmail.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Jacob Keller <jacob.keller@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>,
"Shawn O. Pierce" <spearce@spearce.org>,
Jeff King <peff@peff.net>, Mike Hommey <mh@glandium.org>
Subject: Re: Regarding "git log" on "git series" metadata
Date: Mon, 7 Nov 2016 16:42:04 +0700 [thread overview]
Message-ID: <CACsJy8BDySBWyp3iiLinRkBCew5FNXoQo7z9dMb6w6m9a5X=NA@mail.gmail.com> (raw)
In-Reply-To: <20161107011841.vy2qfnbefidd2sjf@x>
On Mon, Nov 7, 2016 at 8:18 AM, Josh Triplett <josh@joshtriplett.org> wrote:
> Once we have gitrefs, you have both alternatives: reachable (gitref) or
> not reachable (gitlink).
>
> However, if you want some way to mark reachable objects as not
> reachable, such as for a sparse checkout, external large-object storage,
> or similar, then you can use a single unified mechanism for that whether
> working with gitrefs, trees, or blobs.
How? Whether an object reachable or not is baked in the definition (of
either gitlink or gitref). I don't think you can have a "maybe
reachable" type then rely on an external source to determine
reachability,
--
Duy
next prev parent reply other threads:[~2016-11-07 9:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 17:57 Regarding "git log" on "git series" metadata Junio C Hamano
2016-11-04 19:19 ` Jacob Keller
2016-11-04 19:49 ` Jeff King
2016-11-04 21:55 ` Josh Triplett
2016-11-04 23:37 ` Jacob Keller
2016-11-04 23:46 ` Josh Triplett
2016-11-04 23:34 ` Jacob Keller
2016-11-05 1:48 ` Jeff King
2016-11-05 3:55 ` Josh Triplett
2016-11-05 4:41 ` Jeff King
2016-11-05 4:41 ` Junio C Hamano
2016-11-05 4:44 ` Jeff King
2016-11-05 5:00 ` Junio C Hamano
2016-11-04 20:47 ` Christian Couder
2016-11-04 21:19 ` Josh Triplett
2016-11-04 23:04 ` Christian Couder
2016-11-13 17:50 ` Stefano Zacchiroli
2016-11-05 21:56 ` Christian Couder
2016-11-05 4:42 ` Junio C Hamano
2016-11-05 12:17 ` Christian Couder
2016-11-05 12:45 ` Christian Couder
2016-11-05 15:18 ` Josh Triplett
2016-11-05 20:21 ` Christian Couder
2016-11-05 20:25 ` Josh Triplett
2016-11-06 4:50 ` Jacob Keller
2016-11-06 16:34 ` Josh Triplett
2016-11-06 17:14 ` Junio C Hamano
2016-11-06 17:33 ` Josh Triplett
2016-11-06 20:17 ` Jacob Keller
2016-11-07 1:18 ` Josh Triplett
2016-11-07 5:35 ` Jacob Keller
2016-11-07 9:42 ` Duy Nguyen [this message]
2016-11-07 16:11 ` Josh Triplett
2016-11-09 22:57 ` Junio C Hamano
2016-11-04 21:06 ` Josh Triplett
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='CACsJy8BDySBWyp3iiLinRkBCew5FNXoQo7z9dMb6w6m9a5X=NA@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.com \
--cc=josh@joshtriplett.org \
--cc=mh@glandium.org \
--cc=peff@peff.net \
--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).