From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Sixt Subject: Re: How to pull remote branch with specified commit id? Date: Wed, 14 Jan 2009 08:02:36 +0100 Message-ID: <496D8E0C.5060701@viscovery.net> References: <856bfe0e0901130108q3af1345cy31751dd09e030c96@mail.gmail.com> <496C6234.9040903@viscovery.net> <496D0E65.3000200@kitware.com> <20090114165447.qdlwqqfnk4goccgg@webmail.fussycoder.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Brad King , Git Mailinglist To: thestar@fussycoder.id.au X-From: git-owner@vger.kernel.org Wed Jan 14 08:04:08 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1LMznL-00005I-GO for gcvg-git-2@gmane.org; Wed, 14 Jan 2009 08:04:07 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753719AbZANHCk (ORCPT ); Wed, 14 Jan 2009 02:02:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753480AbZANHCk (ORCPT ); Wed, 14 Jan 2009 02:02:40 -0500 Received: from lilzmailso02.liwest.at ([212.33.55.13]:47803 "EHLO lilzmailso02.liwest.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753540AbZANHCj (ORCPT ); Wed, 14 Jan 2009 02:02:39 -0500 Received: from cm56-163-160.liwest.at ([86.56.163.160] helo=linz.eudaptics.com) by lilzmailso02.liwest.at with esmtpa (Exim 4.69) (envelope-from ) id 1LMzls-0000bY-Ak; Wed, 14 Jan 2009 08:02:36 +0100 Received: from [127.0.0.1] (J6T.linz.viscovery [192.168.1.96]) by linz.eudaptics.com (Postfix) with ESMTP id 29E02A865; Wed, 14 Jan 2009 08:02:36 +0100 (CET) User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) In-Reply-To: <20090114165447.qdlwqqfnk4goccgg@webmail.fussycoder.id.au> X-Enigmail-Version: 0.95.5 X-Spam-Score: -1.4 (-) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: thestar@fussycoder.id.au schrieb: >> Johannes Sixt wrote: >>> Consider this: You accidentally push a branch with confidential data >>> to a >>> public repository. You notice it early, and quickly delete the branch >>> using 'git push the-repo :refs/heads/that-branch'. At this time the >>> objects with the confidential data are still lingering in the public >>> repository. But with the current behavior noone can access them even if >>> the SHA1 happens to be known. > > Doesn't this line of reasoning only apply to the ssh and git transports? > (ie, the file and rsync transport would retrieve it regardless) You are right. Http and rsync would happily ship the object. -- Hannes