public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jaroslav Kysela <perex@perex.cz>,
	tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: Request for setup of new repositories
Date: Fri, 29 Apr 2022 11:29:22 +0900	[thread overview]
Message-ID: <YmtNgqfFREYKZM6t@workstation> (raw)
In-Reply-To: <YmfZxmfv5dfgdYG1@workstation>

Hi Jaroslav,

On Tue, Apr 26, 2022 at 08:38:46PM +0900, Takashi Sakamoto wrote:
> Hi Jaroslav,
> 
> On Tue, Apr 26, 2022 at 09:23:38AM +0200, Jaroslav Kysela wrote:
> > On 25. 04. 22 15:20, Takashi Sakamoto wrote:
> > > Hi Jaroslav, Iwai-san,
> > > 
> > > Thanks for your maintenance for alsa-project organization in github.com.
> > > Currently I'd like to add new three repositories under the organization
> > > as a part of my work for ALSA firewire stack.
> > > 
> > > I've been maintaining libhinawa since 2014 and recently realized that
> > > current design is not necessarily convenient since it includes two
> > > functions; operation to Linux FireWire cdev, and operation of ALSA HwDep
> > > cdev. Currently I'm working for new library to split the latter operation.
> > > Then I'd like you to setup below repositories:
> > > 
> > >   * 'libhitaki'
> > >   * 'libhitaki-doc'
> > >   * 'hitaki-rs'
> > > 
> > > The library itself and its Rust binding are utilized by
> > > 'snd-firewire-ctl-services'[2], thus it's preferable to register them under
> > > 'GObject Introspection' Team.
> > > 
> > > Thanks for your assist for my work.
> > 
> > Hi Takashi,
> > 
> > All is set on github. Let me know, if you need other changes.
> 
> Thanks for your arrangement. At present, I have no with for additional
> changes.
> 
> However for settings of libhinwa repository, I'd like you to change URL
> of documentation. We can see it in right side of top page.
> 
>  * https://github.com/alsa-project/libhinawa
> 
> Currently it points to 'https://takaswie.github.io/libhinawa-docs/'
> while it should be 'https://alsa-project.github.io/libhinawa-docs/'.

Additionally today I push documentation for libhitaki into the added
repository:

 * https://github.com/alsa-project/libhitaki-doc
 
I expect Github Pages makes association between the content and publish
URI:

 * https://alsa-project.github.io/libhitaki-doc

However it doesn't. I think we have missing configuration. Would I ask
you to change settings following to this instruction?

https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site


Regards

Takashi Sakamoto

  reply	other threads:[~2022-04-29  2:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 13:20 Request for setup of new repositories Takashi Sakamoto
2022-04-26  7:23 ` Jaroslav Kysela
2022-04-26 11:38   ` Takashi Sakamoto
2022-04-29  2:29     ` Takashi Sakamoto [this message]
2022-05-05 11:41       ` Takashi Sakamoto
2022-05-05 12:10         ` Jaroslav Kysela
2022-05-05 12:49           ` Takashi Sakamoto
2022-05-05 12:59             ` Jaroslav Kysela
2022-05-06  8:56               ` Takashi Sakamoto
2022-05-24 11:25             ` Takashi Sakamoto
2022-05-24 12:36               ` Jaroslav Kysela
2022-05-25  1:42                 ` Takashi Sakamoto
2022-05-25  6:37                   ` Jaroslav Kysela
2022-05-26 12:58                     ` Takashi Sakamoto
2022-05-26 13:35                       ` Jaroslav Kysela
2022-08-05 10:26                         ` Takashi Sakamoto
2022-08-05 10:42                           ` Jaroslav Kysela
2022-08-05 10:58                             ` Takashi Sakamoto
2022-08-27  3:43                               ` Takashi Sakamoto
2022-08-27  5:29                                 ` Jaroslav Kysela
2022-08-27  8:27                                   ` 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=YmtNgqfFREYKZM6t@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --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