Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Kevin Pouget <kevin.pouget@gmail.com>,
	Tom Tromey <tromey@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Handle multiple breakpoint hits in Python interface
Date: Thu, 01 Sep 2011 10:08:00 -0000	[thread overview]
Message-ID: <201109011056.36218.pedro@codesourcery.com> (raw)
In-Reply-To: <CAPftXU+PqqXLUKTu9A6tMZLeCSYtidEgBpN7a8c_66qr+4cxjw@mail.gmail.com>


> --bcaec52e5f83af47d204abdd5b89
> Content-Type: application/octet-stream; 

Please teach your browser to attach files to gmail as
some text based content type, like patch/diff or
text/x-patch.  It may just be a matter of renaming
the files with a ".diff" extension before attaching
them.  If not, you may need to teach your browser
about the mime type of .diff.

You can see which mime type gmail gives your patch
before actually sending the email.  Just let gmail complete
the patch upload, and you should then see something like

[X] 0001-Handle-multiple-breakpoint-hits-in-Python-interface.diff (text/x-patch) 5K

> 	name=0001-Handle-multiple-breakpoint-hits-in-Python-interface
> Content-Disposition: attachment; 
> 	filename=0001-Handle-multiple-breakpoint-hits-in-Python-interface
> Content-Transfer-Encoding: base64
> X-Attachment-Id: f_gs1hwbr01

It also affects the mail archives, check the difference,
both sent from gmail:

 <http://sourceware.org/ml/gdb-patches/2011-08/msg00659.html>
 <http://sourceware.org/ml/gdb-patches/2011-08/msg00570.html>

(follow the "Raw text" link too)

-- 
Pedro Alves


  reply	other threads:[~2011-09-01  9:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTik-ffBpfx4BALF5+Y0xSx_NnaCs7g@mail.gmail.com>
2011-04-22  9:34 ` Kevin Pouget
2011-05-19 18:34   ` Tom Tromey
2011-05-23  9:39     ` Kevin Pouget
2011-05-23 10:51       ` Eli Zaretskii
2011-05-23 11:01         ` Kevin Pouget
2011-05-23 11:59           ` Eli Zaretskii
2011-05-27 20:09       ` Tom Tromey
2011-05-30  7:37         ` Kevin Pouget
2011-05-30  7:49           ` Eli Zaretskii
2011-05-30 10:53             ` Kevin Pouget
2011-08-31 17:49               ` Tom Tromey
2011-09-01  8:36                 ` Kevin Pouget
2011-09-01  8:52                   ` Kevin Pouget
2011-09-01 10:08                     ` Pedro Alves [this message]
2011-09-01 10:18                   ` Eli Zaretskii
2011-09-01 11:41                     ` Kevin Pouget
2011-09-01 15:39                       ` Pedro Alves
2011-09-01 20:53                       ` Eli Zaretskii
2011-09-15 12:34                         ` Kevin Pouget
2011-09-16  7:55                           ` [commit] gdb.python/py-evthreads.exp regression [Re: [PATCH] Handle multiple breakpoint hits in Python interface] Jan Kratochvil
2011-09-16  9:12                             ` Kevin Pouget

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=201109011056.36218.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevin.pouget@gmail.com \
    --cc=tromey@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