From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: request for missing access permission to libhinawa repository
Date: Fri, 7 Aug 2020 23:00:24 +0900 [thread overview]
Message-ID: <20200807140024.GA476204@workstation> (raw)
In-Reply-To: <s5hv9huanoi.wl-tiwai@suse.de>
Hi,
On Fri, Aug 07, 2020 at 10:02:37AM +0200, Takashi Iwai wrote:
> On Fri, 07 Aug 2020 09:52:36 +0200,
> Jaroslav Kysela wrote:
> >
> > Dne 07. 08. 20 v 7:18 Takashi Sakamoto napsal(a):
> > > Hi Iwai-san,
> > >
> > > As Jaroslav is absent so long[1] (summer vacation?), I would like you to
> > > arrange some team/repository settings for libhinawa.
> > >
> > > I lost my write permission to libhinawa repository[2] since Jaroslav's
> > > arrangement for github team. You are an owner of 'alsa-project' team in
> > > github.com, and I guess you have enough permission to configure below items:
> > >
> > > 1. setting enough permission for my account to libhinawa repository
> > > 2. add libhinawa repository to 'GObject Introspection' team[2]
> >
> > Oops. The permissions are fixed now. Sorry for the long delay.
> >
> > Jaroslav
>
> Ah, you already fixed, that's why I didn't find anything wrong :)
At last I can push into the remote branch. Thank you.
And I'd like Jaroslav to fix repository desctiption with correct URL to
documentation so that a few users are not puzzled. At present, it's
https://takaswie.github.io/libhinawa-docs/ but should be
https://alsa-project.github.io/libhinawa-docs/.
Regards
Takashi Sakamoto
prev parent reply other threads:[~2020-08-07 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 5:18 request for missing access permission to libhinawa repository Takashi Sakamoto
2020-08-07 7:52 ` Jaroslav Kysela
2020-08-07 8:02 ` Takashi Iwai
2020-08-07 14:00 ` Takashi Sakamoto [this message]
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=20200807140024.GA476204@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--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.