From: "H.J. Lu" <hjl.tools@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: can't push to binutils-gdb, git-hooks rejecting commits
Date: Tue, 22 Aug 2017 16:11:00 -0000 [thread overview]
Message-ID: <CAMe9rOpYqO3eUeSN9=zwS_XydsQhUbvzaWxeZmj8uB0irci4Rw@mail.gmail.com> (raw)
In-Reply-To: <0704f395-782a-ce48-0dc5-a91cb913ba45@redhat.com>
On Tue, Aug 22, 2017 at 8:28 AM, Pedro Alves <palves@redhat.com> wrote:
> On 08/22/2017 04:22 PM, H.J. Lu wrote:
>> On Tue, Aug 22, 2017 at 8:05 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>>> Hi Pedro,
>>>
>>>> I'm trying to push a patch to master, but it's getting rejected by the
>>>> server-side git hooks. Anyone else seeing the same? See below.
>>>>
>>>> Repeating that big "git rev-list" command below locally shows:
>>>>
>>>> fatal: bad revision '^refs/heads/users/hjl/pr17709'
>>>>
>>>> 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?
>>>
>>> For me, I get a different error message, but in the same vein:
>>>
>>> fatal: bad revision '^refs/heads/users/hjl/gpoff'
>>>
>>> I think it's related to the disk corruption. If the branch stopped
>>> existing, git should have removed the associated reference.
>>>
>>
>> I deleted the old users/hjl/gpoff and pushed a new one.
>
> Eh, that worked, thanks. I managed to push to master now.
> I had thought of trying something like that, but assumed that
> the hooks would reject pushing that too.
>
> Funny that you didn't need to create users/hjl/pr17709.
>
I removed users/hjl/pr17709.
--
H.J.
next prev parent reply other threads:[~2017-08-22 16:11 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 [this message]
2017-08-22 15:31 ` Andreas Schwab
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='CAMe9rOpYqO3eUeSN9=zwS_XydsQhUbvzaWxeZmj8uB0irci4Rw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--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