public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Denis Reva" <denis7774@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: media-sound/zita-ajbridge/
Date: Tue, 22 Sep 2020 15:32:59 +0000 (UTC)	[thread overview]
Message-ID: <1600788768.5e0e5310bf7f29e4a2f1d93fa45bf40981bc6bdc.RarogCmex@gentoo> (raw)

commit:     5e0e5310bf7f29e4a2f1d93fa45bf40981bc6bdc
Author:     Denis Reva <denis7774 <AT> gmail <DOT> com>
AuthorDate: Tue Sep 22 15:25:34 2020 +0000
Commit:     Denis Reva <denis7774 <AT> gmail <DOT> com>
CommitDate: Tue Sep 22 15:32:48 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=5e0e5310

media-sound/zita-ajbridge: maintainer retire #744112

Package-Manager: Portage-3.0.4, Repoman-3.0.1
Signed-off-by: Denis Reva <denis7774 <AT> gmail.com>

 media-sound/zita-ajbridge/metadata.xml | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/media-sound/zita-ajbridge/metadata.xml b/media-sound/zita-ajbridge/metadata.xml
index 317bcc2a..a6d76ea6 100644
--- a/media-sound/zita-ajbridge/metadata.xml
+++ b/media-sound/zita-ajbridge/metadata.xml
@@ -1,11 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM 'http://www.gentoo.org/dtd/metadata.dtd'>
 <pkgmetadata>
-	<maintainer type="person">
-		<email>denis7774@gmail.com</email>
-		<name>Denis Reva</name>
-		<description>RarogCmex</description>
-	</maintainer>
+	<!-- maintainer-needed -->
 	<longdescription lang="en">Zita-ajbridge provides two applications, zita-a2j and zita-j2a. They allow to use an ALSA device as a Jack client, to provide additional capture (a2j) or playback (j2a) channels. Functionally these are equivalent to the alsa_in and alsa_out clients that come with Jack, but they provide much better audio quality. The resampling ratio will typically be stable within 1 PPM and change only very smoothly. Delay will be stable as well even under worse case conditions, e.g. the Jack client running near the end of the cycle.
 
 The theory of operation and internals of these apps are the subject of a paper presented at LAC 2012.


             reply	other threads:[~2020-09-22 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 15:32 Denis Reva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-27 10:32 [gentoo-commits] repo/proj/guru:dev commit in: media-sound/zita-ajbridge/ Ronny Gutbrod
2020-04-25  0:37 Alessandro Barbieri
2020-04-16  9:57 Andrew Ammerlaan
2020-04-13 17:50 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-04-13 17:32 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-04-13 16:55 Andrew Ammerlaan
2020-04-13  6:51 Denis Reva

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=1600788768.5e0e5310bf7f29e4a2f1d93fa45bf40981bc6bdc.RarogCmex@gentoo \
    --to=denis7774@gmail.com \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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