From: Michael Haggerty <mhagger@alum.mit.edu>
Date: Thu, 17 Nov 2011 14:56:08 GMT
Subject: Re: git clone --reference not working
Message-ID: <4EC52088.3030308@alum.mit.edu>
In-Reply-To: <7vr517nvi7.fsf@alter.siamese.dyndns.org>

On 11/17/2011 06:55 AM, Junio C Hamano wrote:
> As a tentative measure, for tonight's pushout, I am inclined to queue an
> equivalent of this patch on top of both mh/ref-api-2 and mh/ref-api-3
> topic and merge them to 'next' and 'pu'. I'd appreciate if you can double
> check the two merges on master..pu after I push them out in a few hours.

I checked the merges in the following (but didn't run the test suite, as
I assume that you have already done that):

   bc1bbe0..09116a1  master     -> gitster/master
   973592c..ada4ec6  mh/ref-api-2 -> gitster/mh/ref-api-2
   caa8069..37817ba  mh/ref-api-3 -> gitster/mh/ref-api-3
   25e8838..cc76151  next       -> gitster/next
 + 06ad567...b032ac4 pu         -> gitster/pu  (forced update)

They all look fine.

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/