Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Clemens Ladisch <clemens@ladisch.de>,
	Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>
Cc: hayashi@clear-code.com,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	linux1394-devel@lists.sourceforge.net,
	"ffado-devel@lists.sf.net" <ffado-devel@lists.sf.net>
Subject: About planning of libhinawa ITP to debian project
Date: Sun, 31 Jan 2016 20:45:44 +0900	[thread overview]
Message-ID: <56ADF3E8.1050109@sakamocchi.jp> (raw)
In-Reply-To: <56ADEF9C.50303@sakamocchi.jp>

Hi,

In this message, I explain about a plan of libhinawa ITP[0] to debian
project. Fortunately, I got a help of a debian package maintainer,
Kentaro Hayashi. He maintains groonga package[1] and experienced
related works[2].

Currently, we plan to work for it in next month, February 2016. I have
no idea about when FTP master acked to our ITP and when the package is
released from debian project.

I with the package will be available as early as possible, and this work
will be a part of his great work as a debian package maintainer.

FYI,

[0] ITP = Intent To Packaging
[1] Debian -- Details of package groonga in sid:
https://packages.debian.org/sid/groonga
[2] Debian Bug report logs - #732055
ITP: groonga -- Fulltext search engine
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732055


Takashi Sakamoto

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

  parent reply	other threads:[~2016-01-31 11:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 11:27 The location of libhinawa and hinawa-utils for FireWire sound devices ? Takashi Sakamoto
2016-01-31 11:44 ` Meaning of the name 'hinawa' and the intension Takashi Sakamoto
2016-01-31 11:45 ` Takashi Sakamoto [this message]
2016-01-31 11:50   ` About planning of libhinawa ITP to debian project Takashi Sakamoto
2016-02-02 14:04   ` Takashi Sakamoto
2016-02-07  3:10     ` Takashi Sakamoto
2016-02-07 13:10       ` Takashi Sakamoto

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=56ADF3E8.1050109@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=ffado-devel@lists.sf.net \
    --cc=hayashi@clear-code.com \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox