From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Clemens Ladisch <clemens@ladisch.de>,
Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: About planning of libhinawa ITP to debian project
Date: Sun, 31 Jan 2016 20:50:21 +0900 [thread overview]
Message-ID: <56ADF4FD.1070703@sakamocchi.jp> (raw)
In-Reply-To: <56ADF3E8.1050109@sakamocchi.jp>
On Jan 31 2016 20:45, Takashi Sakamoto wrote:
> 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
Mmm. My first post seems not to be blasted by the mail server of
alsa-project.org. Please refer to archive of linux1394devel.
The location of libhinawa and hinawa-utils for FireWire sound devices ?
http://sourceforge.net/p/linux1394/mailman/message/34809347/
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2016-01-31 11:50 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 ` About planning of libhinawa ITP to debian project Takashi Sakamoto
2016-01-31 11:50 ` Takashi Sakamoto [this message]
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=56ADF4FD.1070703@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--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 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.