linux-kernel - Re: Is there an recommended way to refer to bitkeepr commits?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8737c8eedy.fsf@linux-m68k.org>
Date:   Sat, 13 May 2017 21:38:17 +0200
From:   Andreas Schwab <schwab@...ux-m68k.org>
To:     Rob Landley <rob@...dley.net>
Cc:     "Eric W. Biederman" <ebiederm@...ssion.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Michael Ellerman <mpe@...erman.id.au>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Al Viro <viro@...iv.linux.org.uk>,
        Oleg Nesterov <oleg@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Is there an recommended way to refer to bitkeepr commits?

On Mai 13 2017, Rob Landley <rob@...dley.net> wrote:

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

You have to use refs/replace/*:refs/replace/* as the refspec for push
and fetch.  By default, push and fetch only look at refs/heads/*.

Andreas.

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