public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@suse.de>
To: Jan Beulich <JBeulich@novell.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: fix for x86-64 failure of testsuite/gcc.dg/titype-1.c
Date: Wed, 09 Jun 2004 17:18:00 -0000	[thread overview]
Message-ID: <40C7341E.5030808@suse.de> (raw)
In-Reply-To: <s0c74079.043@emea1-mh.id2.novell.com>

Jan Beulich wrote:

>Yes, I did. But with all these burocratic rules I'm getting close to
>give up publishing fixes for bugs...
>
This would be very, very sad. However, I think you will understand that 
those
"burocratic rules" are followed by *everyone*: global maintainers, novices,
"normal" contributors... after a while things become rather smooth.

Paolo.

  reply	other threads:[~2004-06-09 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 17:18 Jan Beulich
2004-06-09 17:18 ` Paolo Carlini [this message]
2004-06-09 19:53 ` Jason Merrill
2004-06-10 15:44 ` Gerald Pfeifer
  -- strict thread matches above, loose matches on Subject: below --
2004-06-09 17:08 Jan Beulich
2004-06-09 17:17 ` Paolo Carlini

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=40C7341E.5030808@suse.de \
    --to=pcarlini@suse.de \
    --cc=JBeulich@novell.com \
    --cc=gcc-patches@gcc.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 read-only IMAP folder(s) and NNTP newsgroup(s).