All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Tim Goetze <tim@quitte.de>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: new "in-compatible" alsa-lib PCM API
Date: Thu, 19 Sep 2002 00:17:01 +0900	[thread overview]
Message-ID: <3D8898ED.3040406@boosthardware.com> (raw)
In-Reply-To: Pine.LNX.4.21.0209181615050.630-100000@summer.quitte

Tim Goetze wrote:

> now that i think about it some more, i feel compelled to add:
> 
> this dance around the 0.9.0 version seems ridiculous to me. the
> logical consequence of API changes is bumping the version number,
> and not hiding it in a 'nano' version increment.
> 
> sorry for the harsh words,
> 

So does that mean ALSA has reached 1.1.0?

-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This SF.NET email is sponsored by: AMD - Your access to the experts
on Hammer Technology! Open Source & Linux Developers, register now
for the AMD Developer Symposium. Code: EX8664
http://www.developwithamd.com/developerlab

  parent reply	other threads:[~2002-09-18 15:17 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17 23:15 new "in-compatible" alsa-lib PCM API Chris Rankin
2002-09-18  8:56 ` Jaroslav Kysela
2002-09-18 12:02   ` Chris Rankin
2002-09-18 12:21     ` Jaroslav Kysela
2002-09-18 13:15       ` Tim Goetze
2002-09-18 13:58         ` Thierry Vignaud
2002-09-18 14:19           ` Paul Davis
2002-09-18 15:08             ` Takashi Iwai
2002-09-18 14:50           ` Tim Goetze
2002-09-18 15:07             ` Richard Bown
2002-09-18 15:18               ` Paul Davis
2002-09-18 15:28                 ` Richard Bown
2002-09-18 15:17             ` Patrick Shirkey [this message]
2002-09-18 13:49       ` Paul Davis
2002-09-18 16:51         ` pkg-config (was Re: new "in-compatible" alsa-lib PCM API ) Takashi Iwai
2002-09-18 17:49           ` Andy Lo-A-Foe
2002-09-18 19:26           ` pkg-config Joerg Mayer
2002-09-18 19:46             ` pkg-config Pavel Roskin
2002-09-18 15:00       ` new "in-compatible" alsa-lib PCM API Takashi Iwai
2002-09-18 16:06       ` Jack O'Quin
2002-09-19 15:29         ` Jaroslav Kysela
2002-09-19 19:36           ` Jack O'Quin
2002-09-20 10:20           ` Takashi Iwai
2002-09-20 12:40             ` Kai Vehmanen
2002-09-21  5:41               ` Jaroslav Kysela
2002-09-18 18:58       ` Fernando Pablo Lopez-Lezcano
2002-09-18 21:30       ` Chris Rankin
2002-09-18 21:44         ` Chris Rankin
2002-09-18 12:26     ` Ville Syrjälä
  -- strict thread matches above, loose matches on Subject: below --
2002-09-17 12:58 Jaroslav Kysela
2002-09-17 17:49 ` Kai Vehmanen
2002-09-17 18:29   ` Jaroslav Kysela
2002-09-18  1:08 ` Jack O'Quin
2002-09-18  9:12   ` Jaroslav Kysela
2002-09-18  9:36 ` Takashi Iwai
2002-09-18  9:46   ` Richard Bown
2002-09-18 10:06     ` Takashi Iwai
2002-09-18 10:25       ` Richard Bown
2002-09-18 14:23 ` Kai Vehmanen

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=3D8898ED.3040406@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tim@quitte.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.