Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bart Veer <bartv@ecoscentric.com>
Cc: gdb-patches@sourceware.org
Subject: Re: minor doc fix
Date: Wed, 30 Jul 2008 17:55:00 -0000	[thread overview]
Message-ID: <u63qnp89b.fsf@gnu.org> (raw)
In-Reply-To: <pnbq0ffjuk.fsf@delenn.bartv.net>

> Date: Wed, 30 Jul 2008 16:54:43 +0100
> From: Bart Veer <bartv@ecoscentric.com>
> 
> Current docs for the remote protocol file I/O extension state that a
> struct timeval is 8 bytes. It is actually 12, a 4-byte time_t tv_sec
> and an 8-byte long tv_usec.

You are on a 64-bit machine, right?  On a 32-bit machine, a long takes
4 bytes, like an int.

So if you want to get this text right, you will need to rewrite it
such that it is correct on both architectures.

Thanks.


  reply	other threads:[~2008-07-30 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 15:55 Bart Veer
2008-07-30 17:55 ` Eli Zaretskii [this message]
2008-07-30 18:17   ` Bart Veer
2008-07-30 18:34     ` Eli Zaretskii
2008-07-30 18:49       ` Daniel Jacobowitz
2008-07-30 19:08         ` Eli Zaretskii
2008-07-30 19:15           ` Daniel Jacobowitz
2008-07-30 20:28       ` Bart Veer

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=u63qnp89b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bartv@ecoscentric.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