git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Tan <jonathantanmy@google.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Jonathan Tan <jonathantanmy@google.com>
Subject: Re: What's cooking in git.git (Jan 2021, #04; Sat, 16)
Date: Thu, 21 Jan 2021 10:34:27 -0800	[thread overview]
Message-ID: <20210121183427.1783539-1-jonathantanmy@google.com> (raw)
In-Reply-To: <xmqq8s8so84r.fsf@gitster.c.googlers.com>

> * jt/clone-unborn-head (2020-12-22) 3 commits
>  - clone: respect remote unborn HEAD
>  - connect, transport: add no-op arg for future patch
>  - ls-refs: report unborn targets of symrefs
> 
>  "git clone" tries to locally check out the branch pointed at by
>  HEAD of the remote repository after it is done, but the protocol
>  did not convey the information necessary to do so when copying an
>  empty repository.  The protocol v2 learned how to do so.
> 
>  What's the status of this thing?

Several people have commented on the high-level approach (and I have
addressed those comments), but I don't think anyone has said that the
code itself looks OK. I'll see if I can get some of my colleagues to
review this.

  parent reply	other threads:[~2021-01-21 18:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 21:59 What's cooking in git.git (Jan 2021, #04; Sat, 16) Junio C Hamano
2021-01-21 16:25 ` Elijah Newren
2021-01-21 18:35   ` Junio C Hamano
2021-01-24  5:27     ` Elijah Newren
2021-01-24  7:03       ` Junio C Hamano
2021-01-24  7:10         ` Elijah Newren
2021-01-21 18:34 ` Jonathan Tan [this message]
2021-01-21 21:05   ` Jeff King
2021-01-21 23:10   ` Junio C Hamano

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=20210121183427.1783539-1-jonathantanmy@google.com \
    --to=jonathantanmy@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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;
as well as URLs for NNTP newsgroup(s).