public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@cygnus.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Re: Question about dummy-db.h
Date: Tue, 04 Jan 2000 12:05:00 -0000	[thread overview]
Message-ID: <m3puvhehai.fsf@localhost.localnet> (raw)
In-Reply-To: <u8ogb1sxef.fsf@gromit.rhein-neckar.de>

Andreas Jaeger <aj@suse.de> writes:

> I noticed that struct dbc27 contains:
>   uint32_t lock[14];
> 
> and I don't seem to be able to count until 14 :-(.  The entry looks
> wrong to me.

I don't recall anymore where I looked.  The problem is that db2
interface changes happen from almost every version to the next.  It's
extremely volatile and we might have to add more distinctions.

I'll try to talk to Keith about this problem.

-- 
---------------.      drepper at gnu.org  ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com   `------------------------

      reply	other threads:[~2000-01-04 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-04  6:51 Andreas Jaeger
2000-01-04 12:05 ` Ulrich Drepper [this message]

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=m3puvhehai.fsf@localhost.localnet \
    --to=drepper@cygnus.com \
    --cc=aj@suse.de \
    --cc=libc-hacker@sourceware.cygnus.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).