Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0000920]: 97_debian_alsaconf_cfgfile.dpatch: Change file used by Debian
Date: Tue, 22 Feb 2005 18:07:00 +0100	[thread overview]
Message-ID: <9257978c043916fbfe7bf2ea64cdcd00@bugtrack.alsa-project.org> (raw)


The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=920> 
======================================================================
Reported By:                jdthood
Assigned To:                tiwai
======================================================================
Project:                    ALSA - utils
Issue ID:                   920
Category:                   alsaconf
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Resolution:                 fixed
Fixed in Version:           
======================================================================
Date Submitted:             02-18-2005 22:08 CET
Last Modified:              02-22-2005 18:06 CET
======================================================================
Summary:                    97_debian_alsaconf_cfgfile.dpatch: Change file used
by Debian
Description: 
    Summary: Change the Debian configuration file name

    The patch changes the file name to which alsaconf writes
    if the system is Debian

    Signed-off-by: Thomas Hood <jdthood@yahoo.co.uk>

======================================================================

----------------------------------------------------------------------
 tiwai - 02-22-05 18:06 
----------------------------------------------------------------------
Appled to CVS.  Thanks.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
02-18-05 22:08 jdthood        New Issue                                    
02-18-05 22:08 jdthood        File Added: 97_debian_alsaconf_cfgfile.patch      
             
02-22-05 18:06 tiwai          Status                   new => resolved     
02-22-05 18:06 tiwai          Resolution               open => fixed       
02-22-05 18:06 tiwai          Assigned To               => tiwai           
02-22-05 18:06 tiwai          Note Added: 0003707                          
======================================================================




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-02-22 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 17:07 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-08  8:34 [ALSA - utils 0000920]: 97_debian_alsaconf_cfgfile.dpatch: Change file used by Debian bugtrack
2005-02-18 21:08 bugtrack

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=9257978c043916fbfe7bf2ea64cdcd00@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.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