grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 5/7] add imported "FDT" module for flattened device tree operations
Date: Thu, 04 Apr 2013 15:02:13 -0400	[thread overview]
Message-ID: <515DCE35.7070501@ubuntu.com> (raw)
In-Reply-To: <515DC4CB.8030606@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/4/2013 2:22 PM, Francesco Lavra wrote:
> On 04/02/2013 10:39 PM, Phillip Susi wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Your patches can not be reviewed inline because your mail client
>> is incorrectly setting the mime type to application/octet-stream
>> and the disposition to attachment.  Please fix this.
> 
> Actually the mime types are correct (text/x-csrc and text/x-cdhr).
> You are right about the content disposition though, my mail client
> ignores this option when displaying e-mails so I can actually view
> attachments inline even though the message source says
> differently. Will make sure to have this fixed next time.

Quoting the headers from your original message:

Content-Type: application/octet-stream; name="0005-fdt-support.patch"

Additionally it used base64 encoding so it was treating the file as
binary data, and encoding it to use more space that needed.  Also you
appear to be using the now popular and vile reply-to-list function to
send replies only to the mailing list.  This misfeature breaks cross
posting, non subscribed posters, and delays people from seeing your
response when they do not frequently check all of the mailing lists
they are subscribed to, so please use reply-to-all instead.

See http://david.woodhou.se/reply-to-list.html for more information.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRXc41AAoJEJrBOlT6nu75qH8H/0DRzBi5mJp5jhCTOSvFVOJl
9GlA20pad+IV9qMAKAV1OKe5zCe8izr24uG0Vc8+cH4p8CkieEMwyT36t/4oQ3hl
kkQhJYnlNK9rodsIEoX8jbYvR/7iBbc6g8Bv8EoomAwgEcTVoERD4hpsYgrzZf73
AeSLf/HQAtnOptSwcf9JEHnhXFEubK30DmU7vqW187Brgx2PONwcvv7lLsw8mBXV
Zmk9HOlSAH8fZ1eZ1yX42eN8vlaCEa6VldMpY1ijx2LNaHVBTjXlKTlJvltHyTxU
VXOpEDNjkcNQRpf5oqt9h86O5vt1q86KJQowLauZubcK+K4XED8m8OYaB7CxAQo=
=AaaX
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-04-04 19:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 17:01 [PATCH 5/7] add imported "FDT" module for flattened device tree operations Leif Lindholm
2013-03-30 16:53 ` Francesco Lavra
2013-04-01  2:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 16:42   ` Francesco Lavra
2013-04-07 21:28     ` Francesco Lavra
2013-04-08 18:14     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-17 11:49     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-19 17:36       ` Francesco Lavra
2013-04-02 20:39 ` Phillip Susi
2013-04-04 18:22   ` Francesco Lavra
2013-04-04 19:02     ` Phillip Susi [this message]
2013-04-04 19:15       ` Andrey Borzenkov
2013-04-04 19:33         ` Phillip Susi
2013-04-04 19:46       ` Francesco Lavra

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=515DCE35.7070501@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).