Thread (2 messages) flat view 2 messages, 2 authors, 2016-06-15

Re: git clone --reference not working

From: Michael Haggerty <hidden>
Date: 2016-06-15 22:52:29

Possibly related (same subject, not in this thread)

On 11/17/2011 01:54 AM, Junio C Hamano wrote:
Andrea Arcangeli [off-list ref] writes:
quoted
latest git.git won't clone linux upstream with --reference. Those
v*^{} tags breaks it. What's that stuff anyway, looks totally ugly
(two commits with same data contents and header) bah.
They point at commits they tag, and are essential for auto-following. They
have been there forever in ls-remote output and they are not the real
problem.

A recent topic that was merged at 9bd5000 tightened the refname checking
code without thinking and started to needlessly barf upon seeing them. I
think we have discussed about the issue on the list, but I do not think
there were fixes yet.

Thanks for reminding.

Michael, how does this look?

-- >8 --
Subject: refs: loosen over-strict "format" check
[...]
I reviewed the patch (and ran the test suite here for good measure).
Looks good.
From SubmittingPatches it looks like I should authorize
Reviewed-by: Michael Haggerty <redacted>

Is there a standard way to do so?

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help