From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Request for setup of new repositories
Date: Thu, 26 May 2022 21:58:08 +0900 [thread overview]
Message-ID: <Yo95YGyUSSBOipM2@workstation> (raw)
In-Reply-To: <ef0ab4a6-ed6e-51e5-ffd8-397aa3e289ab@perex.cz>
Hi,
On Wed, May 25, 2022 at 08:37:37AM +0200, Jaroslav Kysela wrote:
> On 25. 05. 22 3:42, Takashi Sakamoto wrote:
> > Thanks for the suggestion. Indeed, we can choose the way to put
> > documentation to specific branch in the repository. I've already
> > investigated the way then had complexed feeling.
> >
> > ...To be honest, I'd like to avoid it, as much as possible, in a point
> > of the essential concept in source control management. The branching
> > idea forces to put several histories disconnected each other into one
> > repository. It's surely available technically, however I feel sort of
> > awkward somehow.
> >
> > (I think I'm enough conservative when using tools. I feel something
> > shooting myself in the foot when doing it. It perhaps comes from my
> > experience under UNIX-like environment...)
> >
> > The separated common repository for documents had room for integration of
> > documentation. For example, I can put library documentations as well as
> > overview page for included software such like Rust crates. It's flexible
> > and logical in a view of top level of software stack.
>
> It's fine for me. The gobject-introspection-docs is created now.
Great. I pushed some documents except for index page:
* https://github.com/alsa-project/gobject-introspection-docs
Later I'd like to use Jekyll backend of github pages[1]. Would I ask you
to grant my privilege in the repository so that I can add configuration
for it? I think the same privilege set in libhinawa-docs is enough.
Additionally, please archive below old documentation repositories? I've
already configure them to publish redirect pages. I hear that github
pages service still publish pages for archived repositories.
* https://github.com/alsa-project/libhinawa-docs/
* https://github.com/alsa-project/libhitaki-doc/
* https://github.com/alsa-project/alsa-gobject-docs/
And it's helpful to change page URL in 'About' section of right pane.
(I think it's good to remove it for convenience.)
* https://github.com/alsa-project/libhinawa/
Today I release new releases for libhinawa and libhitaki. Thanks for
your help.
* https://github.com/alsa-project/libhitaki/releases/tag/v0.1.0
* https://github.com/alsa-project/libhinawa/releases/tag/2.5.0
[1] https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll
[2] https://github.com/alsa-project/libhinawa-docs/
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2022-05-26 12:59 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
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 [this message]
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=Yo95YGyUSSBOipM2@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