Github messages for voidlinux
 help / color / mirror / Atom feed
From: nilium <nilium@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: glusterfs: update to 8.1
Date: Tue, 20 Oct 2020 01:42:24 +0200	[thread overview]
Message-ID: <20201019234224.tjUIU44Jdb1yKm817dJ9LEbsVBOIuYRyErjiRenmiWc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25617@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 746 bytes --]

New comment by nilium on void-packages repository

https://github.com/void-linux/void-packages/pull/25617#issuecomment-712500419

Comment:
I had a comment written up for this but Chrome ate it. Anyway, short form:

This'll need rebasing, so I wouldn't close the PR (pretty sure it's just conflicting on `revision=`). I'd just want to make sure that you test installing this over the top of a 7.x cluster and make sure nothing breaks. I haven't gotten around to 8.x because I'm not in a good spot to test this right now. That said, GlusterFS has been very friendly as far as upgrades go, so I don't think you'd run into anything (and at that point, if it breaks my 7.x cluster, it's probably a GlusterFS bug).

Thanks for working on this!



  parent reply	other threads:[~2020-10-19 23:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15  3:28 [PR PATCH] " ArmedAviator
2020-10-15  3:55 ` ArmedAviator
2020-10-15  4:38 ` ericonr
2020-10-15  6:12 ` [PR PATCH] [Updated] " ArmedAviator
2020-10-15  6:15 ` ArmedAviator
2020-10-15  6:20 ` ArmedAviator
2020-10-15  8:49 ` fosslinux
2020-10-15 13:26 ` [PR PATCH] [Updated] " ArmedAviator
2020-10-15 13:30 ` ArmedAviator
2020-10-16  1:49 ` fosslinux
2020-10-17  5:03 ` ericonr
2020-10-19 23:42 ` nilium
2020-10-19 23:42 ` nilium [this message]
2020-10-19 23:42 ` nilium
2020-10-20  0:48 ` ArmedAviator
2020-11-16 19:29 ` [PR PATCH] [Updated] " ArmedAviator
2020-11-16 19:32 ` ArmedAviator
2020-11-16 19:36 ` ArmedAviator
2020-11-16 19:39 ` ArmedAviator
2020-11-22  3:24 ` [PR PATCH] [Merged]: " the-maldridge

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=20201019234224.tjUIU44Jdb1yKm817dJ9LEbsVBOIuYRyErjiRenmiWc@z \
    --to=nilium@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).