Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: "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 15:05:00 -0000	[thread overview]
Message-ID: <20170822150521.ye7dlqkfcivs5vym@adacore.com> (raw)
In-Reply-To: <abaa0d79-9e13-22fd-f6f8-f8c00596238f@redhat.com>

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 would try a "git fsck" to see if it detects any other kinds of
issues, and decide how to fix them. For instance, we could delete
those branches, and ask HJL to re-push.

I don't think the "git remote prune" command was meant for
that (I think it'll prune references from refs/remotes/ instead).

I can look into this, but as I traveling, availability on my side
is a little spotty.

-- 
Joel


  reply	other threads:[~2017-08-22 15:05 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 [this message]
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
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=20170822150521.ye7dlqkfcivs5vym@adacore.com \
    --to=brobecker@adacore.com \
    --cc=binutils@sourceware.org \
    --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