From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexander Abraham <a.abraham@proxmox.com>
Subject: Re: [pve-devel] [Typo corrected. 2/2] Split a long sentence and corrected some typos.
Date: Thu, 19 Dec 2024 13:32:28 +0100 [thread overview]
Message-ID: <d44cf54a-b7be-4c31-bb79-1b5941876715@proxmox.com> (raw)
In-Reply-To: <20241217101107.43986-3-a.abraham@proxmox.com>
If you send another version of a patch series, please use the
"-v <n>, --reroll-count=<n>" option for "git format-patch".
As long as you are working on a series, you can "change history" on your
local branch. This can be done with "git rebase -i" and "git commit
--amend" and (there are also things like "git absorb"), there are plenty
tutorials on the web.
For the patch at hand, you could fold this change into the previous
patch with "--amend" and just send out the corrected patch by itself and...
Am 17.12.24 um 11:11 schrieb Alexander Abraham:
> ---
...for the corrected patch, put a changelog down here and in the cover
letter.
By prettying up your local git history, the patches will be easier to
review and when applied for real on the shared master branch, the
history will be nice to read :)
Not related to this series and depends on the situations, just
mentioning as a general hint: often one runs into problems during
development, and they might then be missing from the "clean" git
history. It's often worth mentioning those in commit messages, so they
still become a part of history.
> local-zfs.adoc | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/local-zfs.adoc b/local-zfs.adoc
> index bcd02f7..b662233 100644
> --- a/local-zfs.adoc
> +++ b/local-zfs.adoc
> @@ -627,7 +627,8 @@ You *must reboot* to activate these changes.
> SWAP on ZFS
> ~~~~~~~~~~~
>
> -It is strongly recommended to not use a ZFS volume for a swap partition because this could lead to deadlocks freezing thge affected system and other unpredictable behavior. The OpenZFS documentation, which can be viewed https://openzfs.github.io/openzfs-docs/Project%20and%20Community/FAQ.html#using-a-zvol-for-a-swap-device-on-linux[here], warns against using a ZFS volume for a swap partition.
> +It is strongly recommended to not use a ZFS volume for a swap partition because this could lead to deadlocks. These deadlocks could cause the affected system to freeze.
> +The OpenZFS documentation, which can be viewed https://openzfs.github.io/openzfs-docs/Project%20and%20Community/FAQ.html#using-a-zvol-for-a-swap-device-on-linux[here], warns about using a ZFS volume for a swap partition.
>
> [[zfs_encryption]]
> Encrypted ZFS Datasets
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-12-19 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 10:11 [pve-devel] [Typo corrected. 0/2] *** Corrections *** Alexander Abraham
2024-12-17 10:11 ` [pve-devel] [Typo corrected. 1/2] Section on ZFS and swap corrected Alexander Abraham
2024-12-17 10:11 ` [pve-devel] [Typo corrected. 2/2] Split a long sentence and corrected some typos Alexander Abraham
2024-12-19 12:32 ` Fiona Ebner [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=d44cf54a-b7be-4c31-bb79-1b5941876715@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=a.abraham@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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