First: Thanks everyone for your answers. I understand that there is a fetch pack, problem is that I can't force every git server provider to turn it on... Tested with github and they don't seem to have it on by default. I understand that you don't want to allow people fetching single commits all the time, but is there a reason that you don't allow SHA instead of references when you fetch an entire tree? Is there a workaround? Can I somehow ask a remote on a valid reference that includes a SHA? So I can later fetch that reference. In my case I would like to avoid to fetch more then necessary as it pollutes the main repository. -- Magnus MAGNUS CARLSSON Staff Software Engineer ARRIS o: +46 13 36 75 92 e: magnus.carlsson@xxxxxxxxx w: www.arris.com ARRIS: Legal entity: Arris Sweden AB - Registered Office: Teknikringen 2, 583 30 Linkoping, Sweden - Reg No:556518-5831 - VAT No:SE 556518-583 This electronic transmission (and any attached document) is for the sole use of the individual or entity to whom it is addressed. It is confidential and may be attorney-client privileged. In any event the Sender reserves, to the fullest extent, any "legal advice privilege". Any further distribution or copying of this message is strictly prohibited. If you received this message in error, please notify the Sender immediately and destroy the attached message (and all attached documents). ________________________________________ From: Junio C Hamano <gitster@xxxxxxxxx> Sent: Monday, December 18, 2017 19:44 To: Carlsson, Magnus Cc: git@xxxxxxxxxxxxxxx Subject: Re: Fetching commit instead of ref "Carlsson, Magnus" <Magnus.Carlsson@xxxxxxxxx> writes: > ----> So far so good, but then an error message appear: > error: Server does not allow request for unadvertised object 50f730db793e0733b159326c5a3e78fd48cedfec > ----> And nothing seems to be fetched. Yes, that is what the error message is telling you. You'd need to coordinate with the server operator so that the server allows such an request; uploadpack.allowAnySHA1InWant may help.
