Return-Path: 
 <infrastructure-dev-return-2955-apmail-infrastructure-dev-archive=apache.org@apache.org>
X-Original-To: apmail-infrastructure-dev-archive@minotaur.apache.org
Delivered-To: apmail-infrastructure-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3A0D018844
	for <apmail-infrastructure-dev-archive@minotaur.apache.org>;
 Wed,  4 Nov 2015 13:21:25 +0000 (UTC)
Received: (qmail 10693 invoked by uid 500); 4 Nov 2015 13:21:25 -0000
Delivered-To: apmail-infrastructure-dev-archive@apache.org
Received: (qmail 10586 invoked by uid 500); 4 Nov 2015 13:21:24 -0000
Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:infrastructure-dev-help@apache.org>
List-Unsubscribe: <mailto:infrastructure-dev-unsubscribe@apache.org>
List-Post: <mailto:infrastructure-dev@apache.org>
List-Id: <infrastructure-dev.apache.org>
Reply-To: infrastructure-dev@apache.org
Delivered-To: mailing list infrastructure-dev@apache.org
Received: (qmail 10575 invoked by uid 99); 4 Nov 2015 13:21:23 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org)
 (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Nov 2015 13:21:23 +0000
Received: from mail-io0-f175.google.com (mail-io0-f175.google.com
 [209.85.223.175])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with
 ESMTPSA id 8BA1C1A006D
	for <infrastructure-dev@apache.org>; Wed,  4 Nov 2015 13:21:23 +0000 (UTC)
Received: by iody8 with SMTP id y8so52817246iod.1
        for <infrastructure-dev@apache.org>;
 Wed, 04 Nov 2015 05:21:22 -0800 (PST)
X-Gm-Message-State: 
 ALoCoQlNcpit4iHLOaQ6rDgL+b8tg8X5UZhY4NPa/SqZ5Mj1HX53TtoSAz2HPjcl3wzsnQaS96Ms
MIME-Version: 1.0
X-Received: by 10.107.6.23 with SMTP id 23mr3280460iog.147.1446643282510; Wed,
 04 Nov 2015 05:21:22 -0800 (PST)
Received: by 10.50.208.6 with HTTP; Wed, 4 Nov 2015 05:21:22 -0800 (PST)
In-Reply-To: 
 <CAJZRQKwJY1M4W8b0o-CC=yMawnJq-xmeqRZXCasR8B5=-Lb_UQ@mail.gmail.com>
References: 
 <CAKprHVZoW9V46vkE=fVkuYEZxfELzmarSdO-7RQCPS0J9pWp0w@mail.gmail.com>
	<CAFG6u8G1=gZurJrReNwPFsQj_yhLPerR+QLWKF56HOUuZ_UN3A@mail.gmail.com>
	<CAJZRQKwJY1M4W8b0o-CC=yMawnJq-xmeqRZXCasR8B5=-Lb_UQ@mail.gmail.com>
Date: Wed, 4 Nov 2015 14:21:22 +0100
Message-ID: 
 <CAJZRQKy0EtOGod1YEad5f=7JRetQHmf8fZipkWWOFwfFW=mKiA@mail.gmail.com>
Subject: Re: Git, history, protection, and other topics
From: Kristian Rosenvold <krosenvold@apache.org>
To: infrastructure-dev@apache.org
Content-Type: text/plain; charset=UTF-8

Just an example, taken from github:

git clone https://github.com/apache/commons-lang.git
cd commons-lang

< You now have a "complete" commons-lang repo, which you can inspect
with gitk --all or similar>

git config --add remote.origin.fetch
"+refs/pull/*/head:refs/remotes/origin/pull/*"
git fetch

<Watch the fireworks>

Using gitk --all, you'll now see that the "complete" github repo
contains all the pull requests too, github just did not tell us about
them on the initial clone. In the same manner, all historic refs could
be stored.

Kristian