From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] greetings: vb aka vb-linux
Date: Fri, 04 Feb 2022 20:35:00 +0100 [thread overview]
Message-ID: <20220204193500.95H8h3fwhbl75qZ50Plsn3h6LLm0LqVqhO65UfojqkM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35407@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Closed issue by zen0bit on void-packages repository
https://github.com/void-linux/void-packages/issues/35407
Description:
(It isnt really issue I hope)
# I am forking Void linux
and I hope for great cooperation with void devs
Which I offer from the start..
Why I do that?
1. I love void
2. I want branded void linux for desktop on x86_64 platform
3. I want more people use void linux instead of different OS
4. Help promote excellent void linux
5. help promote privacy, security and federation
6. help promote GNU/linux and FOSS in general
7. help create FOSS world bigger
8. because I can
9. have fun
10. learn
@zen0bit from @oSoWoSo
https://osowoso.xyz/vb.html
PS: If void devs or anyone have some suggestion, help, advice etc..
Throw them to me...
I will keep updated this if void dont mind
so you know what I am doing with your grandchild
If you are interested
...
stay in touch...
next prev parent reply other threads:[~2022-02-04 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 17:43 [ISSUE] " zen0bit
2022-02-04 19:34 ` Duncaen
2022-02-04 19:35 ` Duncaen [this message]
2022-02-04 19:35 ` Duncaen
2022-02-04 19:36 ` Duncaen
2022-02-04 19:51 ` zen0bit
2022-02-04 19:52 ` zen0bit
2022-02-04 19:52 ` zen0bit
2022-02-04 19:53 ` zen0bit
2022-02-04 19:55 ` zen0bit
2022-02-04 19:58 ` zen0bit
2022-02-04 19:59 ` zen0bit
2022-02-04 20:02 ` zen0bit
2022-02-04 21:11 ` paper42
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=20220204193500.95H8h3fwhbl75qZ50Plsn3h6LLm0LqVqhO65UfojqkM@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).