From: Jan Vrany <jan.vrany@fit.cvut.cz>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: gdb@sourceware.org, Simon Sobisch <simonsobisch@gnu.org>,
Andrew Burgess <aburgess@redhat.com>
Subject: Re: feature branch for creating MI commands with python (was: How to create new mi commands via python / get current interpreter in python)
Date: Tue, 23 Nov 2021 16:28:32 +0000 [thread overview]
Message-ID: <9df7a0618e8531baafd50e838629cc0783d23558.camel@fit.cvut.cz> (raw)
In-Reply-To: <20211123124819.guu3d6hwq6n4qpko@ubuntu.lan>
On Tue, 2021-11-23 at 12:48 +0000, Lancelot SIX wrote:
> On Tue, Nov 23, 2021 at 12:29:41PM +0000, Jan Vrany wrote:
> > Hi Simon, Andrew
> >
> > > >
> > > > Done. Rebased on a recent master and pushed into branch:
> > > > "users/jv/patches/feature-python-mi":
> > > >
> > > > https://sourceware.org/git/?p=binutils-
> > > > gdb.git;a=shortlog;h=refs/heads/users/jv/patches/feature-
> > > > python-mi
> > > >
> >
> > I have rebased this branch on to of Andrew's patches and
> > wanted to update the feature branch on sourceware.org but
> > it failed:
> >
> > remote: error: denying non-fast-forward
> > refs/heads/users/jv/patches/feature-python-mi (you should pull
> > first)
> >
> > What's the correct way of updating rebased / edited feature branch?
> >
>
> Hi,
>
> When I have to do this and cannot force push to a feature branch, I
> first delete the remote branch, and then push to re-create it.
>
> This could look like something like this (assuming you push the
> remove
> called origin):
>
> git push origin :users/jv/patches/feature-python-mi
> git push origin
> the_name_of_the_local_branch:users/jv/patches/feature-python-mi
>
> Hopefully, this does the trick.
Thanks, that indeed did the trick!
Feature branch updated.
Jan
>
> Best,
> Lancelot.
next prev parent reply other threads:[~2021-11-23 16:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 16:40 How to create new mi commands via python / get current interpreter in python Simon Sobisch
2021-11-02 16:56 ` Jan Vrany
2021-11-02 19:11 ` Simon Sobisch
2021-11-03 9:06 ` Jan Vrany
2021-11-05 18:51 ` Jan Vrany
2021-11-05 21:18 ` feature branch for creating MI commands with python (was: How to create new mi commands via python / get current interpreter in python) Simon Sobisch
2021-11-23 12:29 ` Jan Vrany
2021-11-23 12:48 ` Lancelot SIX
2021-11-23 16:28 ` Jan Vrany [this message]
2021-11-03 16:31 ` How to get the full source location of a frame via python Simon Sobisch
2021-11-03 20:07 ` Jan Vrany
2021-11-03 20:35 ` Simon Sobisch
2021-11-03 20:50 ` UnicodeDecodeError on gdb.execute Simon Sobisch
2021-11-03 21:55 ` Is "forward-search" also possible case insensitive? Simon Sobisch
2021-11-05 9:14 ` Is there a way to know about current "until"/"advance" execution? Simon Sobisch
2021-11-22 14:54 ` Is there a way to get a function's end address other than `disassemble`? Simon Sobisch
2021-11-22 15:14 ` Andreas Schwab
2021-11-22 15:17 ` Simon Sobisch
2021-11-25 19:28 ` Broken source view with Pygments and non-UTF-8 encoded source Simon Sobisch
2021-11-26 11:16 ` Andrew Burgess
2021-11-26 13:39 ` Andrew Burgess
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=9df7a0618e8531baafd50e838629cc0783d23558.camel@fit.cvut.cz \
--to=jan.vrany@fit.cvut.cz \
--cc=aburgess@redhat.com \
--cc=gdb@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=simonsobisch@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).