Re: [PATCH RFC 1/3] cat-file: extract the transport ownership from get_remote_info()
"Pablo Sabater" <pabloosabaterr@gmail.com> writes:
Show 9 quoted lines
> But with that in mind, what if in the future there's a transport without
> smart_options that does support object-info? The smart_options check is
> there because of "this transport can't do object-info", and nothing
> on the object-info path reads smart_options from what I checked.
>
> So I'm going to drop that die(). Later in the code there's already a
> check on transport_fetch_object_info(), which looks for
> fetch_object_info in the transport's vtable. It's a bit later, but it
> checks the real capability and it will give less trouble in the future.
That design decision makes a lot of sense. Thanks.