Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Weimin Pan <weimin.pan@oracle.com>
To: Joel Brobecker <brobecker@adacore.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:32:00 -0000	[thread overview]
Message-ID: <0bb09bd9-812c-0665-3112-353c0e9cef0e@oracle.com> (raw)
In-Reply-To: <20180330225218.fqhgvt7pzaqewic3@adacore.com>



On 3/30/2018 3:52 PM, Joel Brobecker wrote:
> I just emailed Weimin personally when I saw the branch creation,
> but now I understand a little better:
>
>> I just did my first patch:
>>
>> $ git push upstream fixes
>> Enter passphrase for key '/home/wepan/.ssh/id_rsa':
>> Counting objects: 17, done.
>> Delta compression using up to 8 threads.
>> Compressing objects: 100% (10/10), done.
>> Writing objects: 100% (10/10), 2.43 KiB, done.
>> Total 10 (delta 8), reused 0 (delta 0)
>> To ssh://sourceware.org/git/binutils-gdb.git
>>     0f59d5f..c9cf730  fixes -> fixes
>>
>> and hope I did it correctly.
> Actually, no :).
>
> What you did is you pushed your branch called locally "fixes"
> to the repository corresponding to "upstream".  So, when you did
> the "push" command above, what happened is that it created
> the "fixes" branch on the upstream repository. This is not
> what you want, because (1) it creates a branch on the remote
> where you fix is (and pollutes the already existing branches),
> and (2) does not change the "master" branch, and so your fix
> is not really applied to the current development branch either.
>
> With your permission, I will start by fixing the mistake, which
> was to create the "fixes" branch on the upstream repository.
>
> On your end, I think the simplest solution is for you to
> push your current "fixes" branch to upstream's master:
>
>      $ git push upstream fixes:master


$ git push upstream fixes:master
Enter passphrase for key '/home/wepan/.ssh/id_rsa':
To ssh://sourceware.org/git/binutils-gdb.git
  ! [rejected]        fixes -> master (non-fast-forward)
error: failed to push some refs to 
'ssh://sourceware.org/git/binutils-gdb.git'
To prevent you from losing history, non-fast-forward updates were rejected
Merge the remote changes before pushing again.  See the 'Note about
fast-forwards' section of 'git push --help' for details.

Does it mean that I  need to do a "git merge"?

Thanks,
Weimin




  reply	other threads:[~2018-03-30 23:32 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 [this message]
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-03-30 23:32           ` Weimin Pan
2018-03-30 23:45             ` 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=0bb09bd9-812c-0665-3112-353c0e9cef0e@oracle.com \
    --to=weimin.pan@oracle.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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