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 S1758269AbdELRt2 (ORCPT <rfc822;w@1wt.eu>);
        Fri, 12 May 2017 13:49:28 -0400
Received: from mail-out.m-online.net ([212.18.0.10]:33528 "EHLO
        mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1756600AbdELRt1 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 12 May 2017 13:49:27 -0400
X-Auth-Info: PqeO7wnKCrujR9JXkPnFCiuLMbTCrzznC/rSjutxPss5F3QzVVVWX+dlVr06OSSu
From: Andreas Schwab <schwab@linux-m68k.org>
To: Rob Landley <rob@landley.net>
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>
Subject: Re: Is there an recommended way to refer to bitkeepr commits?
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>
X-Yow: Bo Derek ruined my life!
Date: Fri, 12 May 2017 19:49:21 +0200
In-Reply-To: <1638b34f-742d-d718-6ab2-cfed861278e4@landley.net> (Rob Landley's
        message of "Fri, 12 May 2017 11:30:37 -0500")
Message-ID: <87efvuezj2.fsf@linux-m68k.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.)

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."