public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Ruben Safir <ruben@mrbrklyn.com>
Cc: Andrew Pinski <pinskia@gcc.gnu.org>,
	overseers@gcc.gnu.org,  GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Could we start accepting rich-text postings on the gcc lists?
Date: Fri, 23 Nov 2012 20:29:00 -0000	[thread overview]
Message-ID: <CAD_=9DQU3r0jPfq2drXyYp87eUjPg8qoNnTfYWmKTL1_PeriTg@mail.gmail.com> (raw)
In-Reply-To: <20121123201403.GA8026@www2.mrbrklyn.com>

On Fri, Nov 23, 2012 at 3:14 PM, Ruben Safir <ruben@mrbrklyn.com> wrote:
> On Fri, Nov 23, 2012 at 12:12:17PM -0800, Andrew Pinski wrote:
>> On Fri, Nov 23, 2012 at 11:53 AM, Diego Novillo <dnovillo@google.com> wrote:
>> > In this day and age of rich-text capable mailers, restricting postings
>> > to be text-only seems quaint and antiquated.  Are there any hard
>> > requirements that force us to only accept plain text messages?
>
>
> incorrect accessment

I can't parse this.

  reply	other threads:[~2012-11-23 20:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 20:12 Diego Novillo
2012-11-23 20:14 ` Andrew Pinski
2012-11-23 20:24   ` Ruben Safir
2012-11-23 20:29     ` Diego Novillo [this message]
2012-11-23 20:35       ` Ruben Safir
2012-11-23 20:40         ` Diego Novillo
2012-11-23 21:08           ` Ruben Safir
2012-11-23 20:32   ` Diego Novillo
2012-11-23 20:36     ` Ruben Safir
2012-11-24 17:47     ` Ian Lance Taylor
2012-11-24 17:48       ` Robert Dewar
2012-11-24 18:08         ` Daniel Berlin
2012-11-24 18:10           ` Robert Dewar
2012-11-25 15:24             ` Richard Biener
2012-11-25  1:53           ` Ruben Safir
2012-11-24 18:29         ` Jonathan Wakely
2012-11-24 19:43           ` Robert Dewar
2012-11-25 13:58         ` Richard Biener
2012-11-24 17:59       ` Daniel Berlin
2012-11-24 18:13         ` Frank Ch. Eigler
2012-11-24 19:46         ` Ruben Safir
2012-11-25  1:56           ` Daniel Berlin
2012-11-25 13:56         ` Jonathan Larmour
2012-11-25 19:44           ` Diego Novillo
2012-11-26 23:18       ` Gabriel Dos Reis
2012-11-24 10:08   ` Robert Dewar
2012-11-23 21:19 ` Jonathan Larmour
2012-11-23 21:21   ` Diego Novillo
2012-11-23 21:52     ` Paolo Carlini
2012-11-23 23:44     ` Per Bothner
2012-11-24 17:14     ` Corinna Vinschen
2012-11-24 17:57       ` Daniel Berlin
2012-11-24 17:58         ` Daniel Berlin

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='CAD_=9DQU3r0jPfq2drXyYp87eUjPg8qoNnTfYWmKTL1_PeriTg@mail.gmail.com' \
    --to=dnovillo@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=overseers@gcc.gnu.org \
    --cc=pinskia@gcc.gnu.org \
    --cc=ruben@mrbrklyn.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).