Re: [PATCH v2 0/2] do_compare_entry: use already-computed path

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

Subject: Re: [PATCH v2 0/2] do_compare_entry: use already-computed path
From: David Turner <dturner@xxxxxxxxxxxxxxxx>
Date: Mon, 21 Dec 2015 18:33:04 -0500
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <xmqqzix3e61h.fsf@gitster.mtv.corp.google.com>
Organization: Twitter

On Mon, 2015-12-21 at 15:27 -0800, Junio C Hamano wrote:
> Thanks.  Does the number still stay at 25% improvement?

Yes.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- [PATCH v2 0/2] do_compare_entry: use already-computed path
  - From: David Turner
- Re: [PATCH v2 0/2] do_compare_entry: use already-computed path
  - From: Junio C Hamano

Prev by Date: Re: [PATCH v2 0/2] do_compare_entry: use already-computed path
Next by Date: Re: [PATCH 4/4] create_symref: use existing ref-lock code
Previous by thread: Re: [PATCH v2 0/2] do_compare_entry: use already-computed path
Next by thread: Re: [PATCH v2 0/2] do_compare_entry: use already-computed path
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]