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?
Date: Sat, 13 May 2017 21:38:17 +0200 [thread overview]
Message-ID: <8737c8eedy.fsf@linux-m68k.org> (raw)
In-Reply-To: <c4926dfa-5a48-11f5-024f-73bc76f1ba1e@landley.net> (Rob Landley's message of "Sat, 13 May 2017 12:26:53 -0500")
On Mai 13 2017, Rob Landley <rob@landley.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@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-05-13 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 22:04 Is there an recommended way to refer to bitkeepr commits? Eric W. Biederman
2017-05-11 0:47 ` Linus Torvalds
2017-05-11 6:59 ` Michael Ellerman
2017-05-11 16:12 ` Rob Landley
2017-05-12 1:50 ` Michael Ellerman
2017-05-12 7:43 ` Thomas Gleixner
2017-05-12 14:45 ` Eric W. Biederman
2017-05-12 16:30 ` Rob Landley
2017-05-12 17:49 ` Andreas Schwab
2017-05-13 17:26 ` Rob Landley
2017-05-13 19:38 ` Andreas Schwab [this message]
2017-05-13 4:11 ` Eric W. Biederman
2017-05-13 9:35 ` Thomas Gleixner
2017-05-13 17:17 ` Rob Landley
2017-05-12 16:46 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737c8eedy.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox