Re: [RFC PATCH v2 2/4] transport: do not list refs if possible

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [RFC PATCH v2 2/4] transport: do not list refs if possible
From: Stefan Beller <sbeller@xxxxxxxxxx>
Date: Thu, 27 Sep 2018 14:38:42 -0700
Cc: git <git@xxxxxxxxxxxxxxx>, Junio C Hamano <gitster@xxxxxxxxx>
In-reply-to: <61ad64245470e51cb97988e0f2f5ea76c9e2276c.1538075680.git.jonathantanmy@google.com>
References: <20180925225355.74237-1-jonathantanmy@google.com> <cover.1538075680.git.jonathantanmy@google.com> <61ad64245470e51cb97988e0f2f5ea76c9e2276c.1538075680.git.jonathantanmy@google.com>

On Thu, Sep 27, 2018 at 12:24 PM Jonathan Tan <jonathantanmy@xxxxxxxxxx> wrote:

>
> +test_expect_success 'when dynamically fetching missing object, do not list refs' '
> +       cat trace &&

leftover debug cat?

Follow-Ups:
- Re: [RFC PATCH v2 2/4] transport: do not list refs if possible
  - From: Junio C Hamano

References:
- [RFC PATCH] transport: list refs before fetch if necessary
  - From: Jonathan Tan
- [RFC PATCH v2 0/4] Avoid ls-refs when possible in protocol v2
  - From: Jonathan Tan
- [RFC PATCH v2 2/4] transport: do not list refs if possible
  - From: Jonathan Tan

Prev by Date: Re: [PATCH] branch: colorize branches checked out in a linked working tree the same way as the current branch is colorized
Next by Date: Re: [PATCH] Documentation/CodingGuidelines: How to document new APIs
Previous by thread: [RFC PATCH v2 2/4] transport: do not list refs if possible
Next by thread: Re: [RFC PATCH v2 2/4] transport: do not list refs if possible
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux