From: Maxime Devos <maximedevos@telenet.be>
To: Brian Cully <bjc@spork.org>
Cc: 55369@debbugs.gnu.org, Brian Cully <bjc@kublai.com>
Subject: [bug#55369] [PATCH v2] gnu: Change OpenZFS home page to reflect new project ownership.
Date: Thu, 12 May 2022 16:43:41 +0200 [thread overview]
Message-ID: <a09acf0caad93fb6816439507913b6823cbb79bf.camel@telenet.be> (raw)
In-Reply-To: <87v8ualsqd.fsf@ditto.jhoto.spork.org>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
Brian Cully schreef op do 12-05-2022 om 10:36 [-0400]:
> So it looks like the github repository was renamed as things
> merged in from FreeBSD, but the ZFSonLinux project is still extant
> as a Linux-specific resource for ZFS issues:
> https://zfsonlinux.topicbox.com/groups/zfs-discuss/T13eedc32607dab41/zol-repo-move-to-openzfs
>
> I’m ok with dropping this part of the patch. I’d only added it to
> align the github repo (which is openzfs) with the project home
> page. I think it still makes sense to do so, but I’m not terribly
> invested in having this patch applied one way or the other.
Not sure which home page would be the best (the general cross-platform
home page, or the Linux-specific home page), but I'd guess that as
someone interested in OpenZFS you would know the best here.
Summarised: maybe keep the patch?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-12 14:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 13:37 [bug#55369] [PATCH 1/2] gnu: zfs: Use new package style Brian Cully via Guix-patches via
2022-05-11 13:40 ` [bug#55369] [PATCH] gnu: Change OpenZFS home page to reflect new project ownership Brian Cully via Guix-patches via
2022-05-11 14:53 ` [bug#55369] [PATCH 1/2] gnu: zfs: Use new package style Maxime Devos
2022-05-11 14:57 ` Maxime Devos
2022-05-11 15:43 ` [bug#55369] [PATCH v2 " Brian Cully via Guix-patches via
2022-05-11 19:33 ` Maxime Devos
2022-05-11 15:48 ` [bug#55369] [PATCH v2] gnu: Change OpenZFS home page to reflect new project ownership Brian Cully via Guix-patches via
2022-05-11 19:36 ` Maxime Devos
2022-05-12 3:05 ` Brian Cully via Guix-patches via
2022-05-12 14:36 ` Brian Cully via Guix-patches via
2022-05-12 14:43 ` Maxime Devos [this message]
2022-05-12 15:07 ` Brian Cully via Guix-patches via
2022-05-12 15:05 ` [bug#55369] [PATCH v3 1/2] gnu: zfs: Use new package style Brian Cully via Guix-patches via
2022-05-20 18:15 ` bug#55369: [PATCH " Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a09acf0caad93fb6816439507913b6823cbb79bf.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55369@debbugs.gnu.org \
--cc=bjc@kublai.com \
--cc=bjc@spork.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).