From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Wed, 27 Jan 2021 01:28:38 GMT
Subject: Re: [PATCH v5 1/3] ls-refs: report unborn targets of symrefs
Message-ID: <87k0rzp3qx.fsf@evledraar.gmail.com>
In-Reply-To: <32e16dfdbd3f54c0d4b39cbd555e66aa3950fffd.1611686656.git.jonathantanmy@google.com>


On Tue, Jan 26 2021, Jonathan Tan wrote:

> +If the 'unborn' feature is advertised the following argument can be
> +included in the client's request.
> +
> +    unborn
> +	The server may send symrefs pointing to unborn branches in the form
> +	"unborn <refname> symref-target:<target>".
> +

"branches" as in things under refs/heads/*? What should happen if you
send this for a refs/tags/* or refs/xyz/*? Maybe overly pedantic, but it
seems we have no other explicit mention of refs/{heads,tags}/ in
protocol-v2.txt before this[1].

1. Although as I've learned from another recent thread include-tag is
   magical for refs/tags/* only.