Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Abhijit Halder <abhijit.k.halder@gmail.com>
Subject: Re: Some code-cleanup
Date: Mon, 12 Sep 2011 15:30:00 -0000	[thread overview]
Message-ID: <201109121623.04292.pedro@codesourcery.com> (raw)
In-Reply-To: <CAOhZP9xK6f=96Gxj2To-ktVK7qA1k=Wek7hX-FMwq8u75KsDyw@mail.gmail.com>

On Monday 12 September 2011 16:05:59, Abhijit Halder wrote:
> I have seen in one place (write_exp_elt) that we are passing an union
> by value and not by reference.
> Please let me know whether we do have any specific reason of doing
> that. I am submitting the patch as an attachment. Please review the
> same.
> 

See <http://sourceware.org/cgi-bin/get-raw-msg?listname=gdb-patches&date=2011-09&msgid=CAOhZP9xK6f%3D96Gxj2To-ktVK7qA1k%3DWek7hX-FMwq8u75KsDyw%40mail.gmail.com>:

--0016364d2c7965a8ac04acbfddf0
Content-Type: application/octet-stream; name=patch
Content-Disposition: attachment; filename=patch
Content-Transfer-Encoding: base64
X-Attachment-Id: f_gshl4bmu0

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 to have a ".diff" or ".patch" extension before
attaching them.  If not, you may need to teach your browser
about the mime type of .diff/.patch.

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] foo.diff (text/x-patch) 5K

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

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

(follow the "Raw text" link too)

-- 
Pedro Alves


  reply	other threads:[~2011-09-12 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12 15:08 Abhijit Halder
2011-09-12 15:30 ` Pedro Alves [this message]
2011-09-12 16:05   ` Abhijit Halder
2011-09-13 12:20     ` Jan Kratochvil
2011-09-13 12:55       ` Abhijit Halder
2011-09-14  5:04         ` Jan Kratochvil
2011-09-14  6:32           ` Abhijit Halder
2011-09-15  9:09             ` Jan Kratochvil
2011-09-16 10:34               ` Abhijit Halder
2011-09-16 14:44                 ` Jan Kratochvil
2011-09-16 14:47                   ` Abhijit Halder

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=201109121623.04292.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=abhijit.k.halder@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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