Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: manjo@austin.ibm.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] (Resubmit) Use HAVE_LONGLONG instead of __GNUC__ to check for long long support.
Date: Tue, 19 Apr 2005 21:50:00 -0000	[thread overview]
Message-ID: <20050419215026.GA13325@nevyn.them.org> (raw)
In-Reply-To: <200504192146.j3JLkgwf015869@elgar.sibelius.xs4all.nl>

On Tue, Apr 19, 2005 at 11:46:42PM +0200, Mark Kettenis wrote:
>    Date: Tue, 19 Apr 2005 17:36:34 -0400
>    From: Daniel Jacobowitz <drow@false.org>
> 
>    On Tue, Apr 19, 2005 at 05:06:28PM -0500, Manoj Iyer wrote:
>    > 
>    > 
>    > Anymore thoughts on this patch? ok to commit?
> 
>    Please wait a bit.  I asked Mark a question, and I haven't had time to
>    go digging for the answer myself yet.  It's only been a couple of
>    hours.
> 
> Oops.  I just sent out an ok.  I can vaguely remember something but
> it's gotten a bit mixed up with with the what I remember about the
> `long double' check in the gdb configure.ac.

That's probably it.  Well, we'll find out.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-19 21:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 22:41 [RFC] " Manoj Iyer
2005-04-18 22:52 ` Daniel Jacobowitz
2005-04-18 23:15   ` Manoj Iyer
2005-04-19  7:58     ` M.M. Kettenis
2005-04-19  9:54       ` Manoj Iyer
2005-04-19 10:24         ` [RFC] (Resubmit) " Manoj Iyer
2005-04-19 21:33           ` Manoj Iyer
2005-04-19 21:36             ` Daniel Jacobowitz
2005-04-19 21:48               ` Mark Kettenis
2005-04-19 21:50                 ` Daniel Jacobowitz [this message]
2005-04-19 21:43             ` Mark Kettenis
2005-04-19 12:33       ` [RFC] " Daniel Jacobowitz
2005-04-19 14:56         ` Manoj Iyer

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=20050419215026.GA13325@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=manjo@austin.ibm.com \
    --cc=mark.kettenis@xs4all.nl \
    /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