From: Andreas Schwab <schwab@suse.de>
To: Pedro Alves <palves@redhat.com>
Cc: "binutils\@sourceware.org" <binutils@sourceware.org>,
"gdb\@sourceware.org" <gdb@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: can't push to binutils-gdb, git-hooks rejecting commits
Date: Tue, 22 Aug 2017 15:31:00 -0000 [thread overview]
Message-ID: <mvmr2w3liuy.fsf@suse.de> (raw)
In-Reply-To: <abaa0d79-9e13-22fd-f6f8-f8c00596238f@redhat.com> (Pedro Alves's message of "Tue, 22 Aug 2017 15:56:06 +0100")
On Aug 22 2017, Pedro Alves <palves@redhat.com> wrote:
> Repeating that big "git rev-list" command below locally shows:
>
> fatal: bad revision '^refs/heads/users/hjl/pr17709'
You need to translate all refs to your remote-tracking branches inside
origin (eg. refs/remotes/origin/users/hjl/pr17709), or run that command
inside a bare mirror. Doing that results in no error, execpt that the
first rev does not exist for me, but that is probably the rev you are
about to push.
> That branch doesn't appear to exist anymore. Sounds like the hooks
> need to run "git remote prune origin" on their clone? Does that make
> sense?
The hook is running directly inside the bare repository, there is no
remote.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2017-08-22 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 14:56 Pedro Alves
2017-08-22 15:05 ` Joel Brobecker
2017-08-22 15:17 ` Pedro Alves
2017-08-22 17:33 ` Joel Brobecker
2017-08-22 19:32 ` Joel Brobecker
2017-08-22 19:48 ` Pedro Alves
2017-08-22 15:22 ` H.J. Lu
2017-08-22 15:28 ` Pedro Alves
2017-08-22 16:11 ` H.J. Lu
2017-08-22 15:31 ` Andreas Schwab [this message]
2017-08-22 20:08 ` Joseph Myers
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=mvmr2w3liuy.fsf@suse.de \
--to=schwab@suse.de \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
/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