This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: can't push to binutils-gdb, git-hooks rejecting commits
- From: Andreas Schwab <schwab at suse dot de>
- To: Pedro Alves <palves at redhat dot com>
- Cc: "binutils\@sourceware.org" <binutils at sourceware dot org>, "gdb\@sourceware.org" <gdb at sourceware dot org>, Joel Brobecker <brobecker at adacore dot com>
- Date: Tue, 22 Aug 2017 17:31:17 +0200
- Subject: Re: can't push to binutils-gdb, git-hooks rejecting commits
- Authentication-results: sourceware.org; auth=none
- References: <abaa0d79-9e13-22fd-f6f8-f8c00596238f@redhat.com>
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."