From: Pedro Alves <palves@redhat.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
GDB Patches <gdb-patches@sourceware.org>,
Luis Machado <lgustavo@codesourcery.com>
Subject: Re: [PATCH] bfd: Fix regression when building bfd on mingw32
Date: Tue, 04 Aug 2015 16:14:00 -0000 [thread overview]
Message-ID: <55C0E4F6.5080703@redhat.com> (raw)
In-Reply-To: <CABOHX+dKK8ke0JZDjdcaHYdsYv==ksHGx7Z+YpiW=ijqRvc=Bw@mail.gmail.com>
On 08/04/2015 05:09 PM, Iain Buclaw wrote:
> Will have to wait until this evening if that's OK.
That's super fine.
> Is there a general
> guideline on pushing patches to branch? I assume that you don't do
> anything fancy with git such as merge or cherry-pick.
Nothing fancy. non-fast-forward merges are disabled, the server
rejects them. So to push to branch, simply rebase the patch on top of
the branch and then push to it. cherry-picking is fine as it's just a
way to get the patch in the first place.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-08-04 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 19:14 Iain Buclaw
2015-08-04 15:42 ` Joel Brobecker
2015-08-04 15:51 ` Iain Buclaw
2015-08-04 15:54 ` Joel Brobecker
2015-08-04 15:55 ` Pedro Alves
2015-08-04 16:09 ` Iain Buclaw
2015-08-04 16:14 ` Pedro Alves [this message]
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=55C0E4F6.5080703@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.org \
--cc=lgustavo@codesourcery.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