public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Pedro Alves <palves@redhat.com>
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:09:00 -0000	[thread overview]
Message-ID: <CABOHX+dKK8ke0JZDjdcaHYdsYv==ksHGx7Z+YpiW=ijqRvc=Bw@mail.gmail.com> (raw)
In-Reply-To: <55C0E066.9040805@redhat.com>

On 4 August 2015 at 17:55, Pedro Alves <palves@redhat.com> wrote:
> On 08/04/2015 04:51 PM, Iain Buclaw wrote:
>
>> Actually, I got redirected to the binutils ml in the other thread,
>> it's already been submitted and pushed in.
>>
>> https://sourceware.org/ml/binutils/2015-07/msg00305.html
>> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=d6f1bafa2c05241b89c0303a9f6a2af89f51c39c
>>
>> So if you are having difficulties reproducing...
>
> I think this should be pushed to the 7.10 branch as well.
> Could you handle that?
>
> Thanks,
> Pedro Alves
>

Will have to wait until this evening if that's OK.  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.

Regards
Iain

  reply	other threads:[~2015-08-04 16:09 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 [this message]
2015-08-04 16:14         ` Pedro Alves

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='CABOHX+dKK8ke0JZDjdcaHYdsYv==ksHGx7Z+YpiW=ijqRvc=Bw@mail.gmail.com' \
    --to=ibuclaw@gdcproject.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).