All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobin Davis <tdavis@dsl-only.net>
To: James C Georgas <jgeorgas@rogers.com>
Cc: alsa-devel@lists.sourceforge.net,
	James Courtier-Dutton <James@superbug.co.uk>
Subject: Re: ac97 maintenance
Date: Wed, 06 Dec 2006 11:38:00 -0800	[thread overview]
Message-ID: <1165433880.32312.243.camel@razman> (raw)
In-Reply-To: <1165433043.23056.17.camel@Rainsong>


[-- Attachment #1.1: Type: text/plain, Size: 1668 bytes --]

Takashi usually applies the patches that are sent to the mailing list,
but he is currently out on vacation.  He's really good about catching up
on these things, though, so it will make it in (unless there is a
programming issue, which he will let you know about).

I don't think there is really a formal process, though.  Personally, I'd
rather submit my patches to the list for review than directly into the
repository.  Helps me learn the correct coding style.

Tobin

On Wed, 2006-12-06 at 14:24 -0500, James C Georgas wrote:

> On Wed, 2006-06-12 at 19:18 +0000, James Courtier-Dutton wrote:
> > James C Georgas wrote:
> > > Who is maintaining the ac97 stuff these days?
> > > 
> > 
> > What sort of question is that?
> > If you have a problem, raise a bug report.
> > There are quite a few developers that can fix bugs in that bit of code.
> > 
> > 
> > James
> 
> The reason I asked is that I can't log into the bugtrack system for some
> reason, so I wanted to send a patch directly to a maintainer. I posted
> the patch it to the group last Friday, but I don't think anyone noticed
> it.
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel

-- 
Tobin Davis <tdavis@dsl-only.net>

[-- Attachment #1.2: Type: text/html, Size: 3020 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

  reply	other threads:[~2006-12-06 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 12:00 Creating a new hardware Sound4 - Camille Gonnet
2006-12-06 19:08 ` ac97 maintenance James C Georgas
2006-12-06 19:18   ` James Courtier-Dutton
2006-12-06 19:24     ` James C Georgas
2006-12-06 19:38       ` Tobin Davis [this message]
2006-12-06 19:39       ` Randy Cushman
2006-12-06 19:44         ` Jaroslav Kysela
  -- strict thread matches above, loose matches on Subject: below --
2006-12-06 20:18 James C Georgas

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=1165433880.32312.243.camel@razman \
    --to=tdavis@dsl-only.net \
    --cc=James@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jgeorgas@rogers.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 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.