Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Patrick Palka <patrick@parcs.ath.cx>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix terminal state corruption when starting a program from within TUI
Date: Wed, 27 Aug 2014 16:21:00 -0000	[thread overview]
Message-ID: <CA+C-WL_aHvRounAqChZX+TNxsbS2437ywKGEn8sNW1A7vdZdTQ@mail.gmail.com> (raw)
In-Reply-To: <87wq9t6h8v.fsf@redhat.com>

On Wed, Aug 27, 2014 at 12:15 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> On Wednesday, August 27 2014, Patrick Palka wrote:
>
>> Note that I don't have commit access so I would appreciate if someone
>> would
>> commit this on my behalf.
>
> Thanks a lot for the patch :-).  TUI needs some love, and it is always
> nice to see patches for it!
>
> I just noticed you don't have copyright assignment on file, right?
> Since your patch is not trivial, I believe you will have to sign the
> copyright assignment to FSF before we can push the patch for you.  I am
> sending you the form off-list; it is a simple procedure, but it can take
> 1 or 2 months depending on your location.
>
> If you do have copyright assignment on file, please let me know and I
> can push the patch right away.

Thanks.  I should have a copyright assignment on file for binutils and
for GDB.  I completed this process back in January.


  reply	other threads:[~2014-08-27 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25 18:18 Patrick Palka
2014-08-27 11:41 ` Pedro Alves
2014-08-27 12:19   ` Patrick Palka
2014-08-27 16:15     ` Sergio Durigan Junior
2014-08-27 16:21       ` Patrick Palka [this message]
2014-08-27 16:28         ` Sergio Durigan Junior
2014-08-27 16:37     ` Sergio Durigan Junior
2014-08-27 16:43       ` Patrick Palka
2014-08-27 16:50         ` Sergio Durigan Junior
2014-08-27 16:55           ` Patrick Palka
2014-08-27 17:02             ` Sergio Durigan Junior

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=CA+C-WL_aHvRounAqChZX+TNxsbS2437ywKGEn8sNW1A7vdZdTQ@mail.gmail.com \
    --to=patrick@parcs.ath.cx \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=sergiodj@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