git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>, git@vger.kernel.org
Subject: Re: git clone --reference not working
Date: Thu, 17 Nov 2011 15:56:08 +0100	[thread overview]
Message-ID: <4EC52088.3030308@alum.mit.edu> (raw)
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/

  reply	other threads:[~2011-11-17 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111116234314.GF3306@redhat.com>
2011-11-17  0:54 ` git clone --reference not working Junio C Hamano
2011-11-17  4:49   ` Michael Haggerty
2011-11-17  5:55     ` Junio C Hamano
2011-11-17 14:56       ` Michael Haggerty [this message]
2011-11-17 17:40         ` 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=4EC52088.3030308@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=aarcange@redhat.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).