Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Anton Kolesov <Anton.Kolesov@synopsys.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"Jeremy.bennett@embecosm.com" <Jeremy.bennett@embecosm.com>
Subject: RE: [PATCH] testsuite: Fix gdb.base/bang.exp for remote stubs without exit
Date: Fri, 25 Oct 2013 15:27:00 -0000	[thread overview]
Message-ID: <39A54937CC95F24AA2F794E2D2B66B1356BDC3B3@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <526A65C0.2050102@redhat.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1041 bytes --]

> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: 25 October 2013 16:36
> To: Anton Kolesov
> Cc: gdb-patches@sourceware.org; Jeremy.bennett@embecosm.com
> Subject: Re: [PATCH] testsuite: Fix gdb.base/bang.exp for remote stubs
> without exit
> 
> 
> Done, as below.  Thanks for the patch.


> 
> Note I fixed a spurious whitespace:
>  $ git am /tmp/mbox
>  Applying: testsuite: Fix gdb.base/bang.exp for remote stubs without exit
>  /home/pedro/gdb/mygit/src/.git/rebase-apply/patch:23: trailing
> whitespace.
>  gdb_continue_to_end "" continue 1
>  warning: 1 line adds whitespace errors.
> 
> And also fixed ChangeLog entry formatting -- should be two spaces
> between name and email.
> 
> ("tiny change" is just how we mark patches that don't add up
> to something legally significant.)

Thanks. I will talk to management and legal department to sort out copyright issues. I will pay greater attention to those details.

Anton Kolesov



\x16º&Öéj×!zÊÞ¶êç×NºóÉb²Ö«r\x18\x1dn–­r\x17¬

      reply	other threads:[~2013-10-25 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  8:58 Anton Kolesov
2013-10-09 11:28 ` Pedro Alves
2013-10-25 10:04   ` Anton Kolesov
2013-10-25 12:22     ` Pedro Alves
2013-10-25 12:36       ` Pedro Alves
2013-10-25 15:27         ` Anton Kolesov [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=39A54937CC95F24AA2F794E2D2B66B1356BDC3B3@de02wembxa.internal.synopsys.com \
    --to=anton.kolesov@synopsys.com \
    --cc=Jeremy.bennett@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --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