Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Weimin Pan <weimin.pan@oracle.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH5 PR gdb/16959] gdb hangs in infinite recursion
Date: Fri, 30 Mar 2018 23:45:00 -0000	[thread overview]
Message-ID: <20180330234535.pd2byddajqbezkpr@adacore.com> (raw)
In-Reply-To: <46f00b2c-cf52-c50d-1948-4cdfb3b598bd@oracle.com>

> > With your permission, I will start by fixing the mistake, which
> > was to create the "fixes" branch on the upstream repository.
> 
> Yes, please go ahead. Thanks.

FTR, done. This is how I did it:

    $ git push origin :fixes
    remote: fatal: Invalid revision range c9cf7302418ad14b7f72949ba0421b9df3cd1127..0000000000000000000000000000000000000000
    To ssh://sourceware.org/git/binutils-gdb.git
     - [deleted]               fixes

The error is a limitation of one the the scripts that get run
when we create or delete a new branch or a new tag, but is not
fatal. The output confirms the branch we deleted.

-- 
Joel


  reply	other threads:[~2018-03-30 23:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 21:11 Weimin Pan
2018-03-30  5:09 ` Simon Marchi
2018-03-30 21:44   ` Weimin Pan
2018-03-30 22:05     ` Simon Marchi
2018-03-30 22:39       ` Weimin Pan
2018-03-30 22:52         ` Joel Brobecker
2018-03-30 23:32           ` Weimin Pan
2018-03-30 23:45             ` Joel Brobecker [this message]
2018-03-30 23:32           ` Weimin Pan
2018-03-30 23:41             ` Joel Brobecker
2018-03-31  0:31               ` Weimin Pan
2018-03-31  1:52                 ` Joel Brobecker
2018-03-31  3:32                   ` Wei-min Pan
2018-04-02 13:44                     ` Joel Brobecker
2018-04-02 17:27                       ` Wei-min Pan
2018-04-02 17:53                         ` Joel Brobecker
2018-04-02 19:28   ` [pushed][PATCH5 " Weimin Pan

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=20180330234535.pd2byddajqbezkpr@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=weimin.pan@oracle.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