All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ivica Ico Bukvic" <ico@fuse.net>
To: 'Russell King' <rmk+alsa@arm.linux.org.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: RE: snd-hdsp oddities
Date: Mon, 5 Jul 2004 11:51:46 -0400	[thread overview]
Message-ID: <20040705155127.LTDI27242.smtp3.fuse.net@64BitBadass> (raw)
In-Reply-To: <20040705130008.B25490@flint.arm.linux.org.uk>

Your posts are not being rejected for "no reason," but because you need to
subscribe to the list to be able to post (just like the alsa-dev list). That
being said, I am cross-posting exactly for this reason, as I want to target
both the subscribers of lad and alsa-dev as this pertains to both groups
(especially because some of the members, such as yourself, are subscribed to
just one of these).

What I can do, however, is try to use bcc fields so that way you should
never see the other lists this has been cross-posted to and therefore your
e-mailing client should never reply to them either. This, however will still
require you to make sure that a copy of your e-mail reaches the alsa-dev
list by adding it to the cc: field and therefore will ask for the same
amount of attention as just removing lad list from the list of recipients...

Best wishes,

Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico/
 

> -----Original Message-----
> From: Russell King [mailto:rmk@arm.linux.org.uk] On Behalf Of Russell King
> Sent: Monday, July 05, 2004 8:00 AM
> To: ico@fuse.net
> Cc: alsa-devel@lists.sourceforge.net
> Subject: Re: [Alsa-devel] snd-hdsp oddities
> 
> Could you please refrain from cross posting between here and the
> linux-audio-dev mailing list?
> 
> For those of us who aren't on the linux-audio-dev list, we regularly
> get our replies rejected for no reason by the moderator there.  (See
> attached message.)
> 
> Thanks.
> 
> --
> Russell King
>  Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
>  maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
>                  2.6 Serial core




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

  reply	other threads:[~2004-07-05 15:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02  0:22 snd-hdsp oddities ico-rDkNP/OoUoU
     [not found] ` <20040702002208.KXUI17933.smtp2.fuse.net-TAIDijpykVYqcZcGjlUOXw@public.gmane.org>
2004-07-02  2:16   ` Paul Davis
2004-07-02  7:32     ` Re: [linux-audio-dev] " Russell King
     [not found]     ` <200407020216.i622GdaC002355-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2004-07-02  9:40       ` [Alsa-devel] " Takashi Iwai
     [not found]         ` <s5h7jtmags3.wl-UC7Roit8zEholqkO4TVVkw@public.gmane.org>
2004-07-02 11:26           ` Florian Schmidt
     [not found]             ` <20040702132644.3697ed1d-1azMibUuNldkksQ3EBHwWw@public.gmane.org>
2004-07-02 12:30               ` Takashi Iwai
2004-07-05 12:00 ` Russell King
2004-07-05 15:51   ` Ivica Ico Bukvic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-02 12:56 ico-rDkNP/OoUoU

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=20040705155127.LTDI27242.smtp3.fuse.net@64BitBadass \
    --to=ico@fuse.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rmk+alsa@arm.linux.org.uk \
    /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.