From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1756807AbdEMR07 (ORCPT <rfc822;w@1wt.eu>);
        Sat, 13 May 2017 13:26:59 -0400
Received: from mail-qk0-f196.google.com ([209.85.220.196]:33773 "EHLO
        mail-qk0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1755299AbdEMR05 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 13 May 2017 13:26:57 -0400
Subject: Re: Is there an recommended way to refer to bitkeepr commits?
To: Andreas Schwab <schwab@linux-m68k.org>
References: <87k25ol41u.fsf@xmission.com>
 <CA+55aFxj4Oe8+DbNLzk+SKoW99MTeF+m1SAiC4hgW=bN2dpvEQ@mail.gmail.com>
 <87h90rj2ub.fsf@concordia.ellerman.id.au>
 <1de8bc32-ebac-141a-080a-ef1c5a149904@landley.net>
 <87r2zuc08d.fsf@concordia.ellerman.id.au>
 <alpine.DEB.2.20.1705120941060.1800@nanos> <87shka2kxn.fsf@xmission.com>
 <1638b34f-742d-d718-6ab2-cfed861278e4@landley.net>
 <87efvuezj2.fsf@linux-m68k.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Michael Ellerman <mpe@ellerman.id.au>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Al Viro <viro@zeniv.linux.org.uk>, Oleg Nesterov <oleg@redhat.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
From: Rob Landley <rob@landley.net>
Message-ID: <c4926dfa-5a48-11f5-024f-73bc76f1ba1e@landley.net>
Date: Sat, 13 May 2017 12:26:53 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <87efvuezj2.fsf@linux-m68k.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 05/12/2017 12:49 PM, Andreas Schwab wrote:
> On Mai 12 2017, Rob Landley <rob@landley.net> wrote:
> 
>> Last I checked I couldn't just "git push" the fullhist tree to
>> git.kernel.org because git graft didn't propagate right.
> 
> Perhaps you could recreate them with git replace --graft.  That creates
> replace objects that can be pushed and fetched.  (They are stored in
> refs/replace, and must be pushed/fetched explicitly.)

It's the "must be pushed/fetched explicitly" part that I couldn't figure
out back when I tried it.

I inherited this tree from somebody who made it. I noticed its existence
because lwn.net covered it, and then 6 months later it had vanished
without trace (as so many things do). I reproduced it from the build
script (if you can't reproduce the experiment from initial starting
conditions, it's not science), went "look, cool thing", and hosted a
copy with an occasional repaint.

I would be _thrilled_ to hand it off to somebody who knows what they're
doing with git. I'm just unusually interested in computer history and
the preservation thereof. (https://landley.net/history/mirror).

Rob