git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git clone --reference not working

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 17, 2011, 05:55 UTC
Message-ID
<7vr517nvi7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4EC4926D.5050004@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
Show 9 quoted lines
> On 11/17/2011 01:54 AM, Junio C Hamano wrote:
> ...
> Looks good.
>
>>From SubmittingPatches it looks like I should authorize
>
> Reviewed-by: Michael Haggerty <mhagger@alum.mit.edu>
>
> Is there a standard way to do so?

That's perfect. I asked for an extra set of eyeballs from somebody who is familiar with the codepath that had a problem, and that person eyeballed and found the change to be an appropriate fix to the problem.

Either Acked-by or Reviewed-by is fine by me.

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.

Thanks.
Previous: Michael HaggertyNext: Michael Haggerty
Message 3 of 5 in “Re: git clone --reference not working”
  1. Junio C HamanoNov 17, 2011
  2. Michael HaggertyNov 17, 2011
  3. Junio C HamanoNov 17, 2011
  4. Michael HaggertyNov 17, 2011
  5. Junio C HamanoNov 17, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.