all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH] ha: Correct in-text references to Available HA Rule Types
Date: Tue, 02 Sep 2025 14:26:04 +0200	[thread overview]
Message-ID: <DCIBA8J3USHP.G8NMJFOM7I59@proxmox.com> (raw)
In-Reply-To: <DCIB6GALM3VO.17DBQC8K1CBP5@proxmox.com>

On Tue Sep 2, 2025 at 2:21 PM CEST, Daniel Kral wrote:
> On Tue Sep 2, 2025 at 1:48 PM CEST, abobakr mohammed wrote:
>> Corrected the descriptions of affinity rules in Table 2 (they were previously reversed).
>> Changed "seperate" to "negative".
>>
>> Signed-off-by: abobakr mohammed <a.mohammed@proxmox.com>
>
> Thanks for spotting this and sending a patch!
>
> A few small points:
>
> The PATCH in the subject line should be "PATCH pve-docs" or just
> "PATCH docs", so everyone knows which repository it belongs to ;). You
> can do that by using
>
>     git format-patch --subject-prefix="PATCH docs" -v2 ...
>
> when formatting the patch. We usually use only lowercase for the subject
> line too, but that's more nit-picking from my side.

actually, you may prefer to put that into the repos `.git/config` file
like so:

```
[format]
	subjectprefix = PATCH docs
	signoff = true
```

`git format-patch` will then always add a sign off line and the correct
subject line. safes time and you can't accidentally forget to do it :)

>
> The commit message should be imperative (e.g. "Change X to Y" instead of
> "Changes/Changed X to Y") and the line length must not be longer than 72
> characters. See [0] for more information.
>
> [0] https://pve.proxmox.com/wiki/Developer_Documentation#Commits_and_Commit_Messages
>
> With those addressed, consider this as:
>
> Reviewed-by: Daniel Kral <d.kral@proxmox.com>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2025-09-02 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 11:48 abobakr mohammed
2025-09-02 12:21 ` Daniel Kral
2025-09-02 12:26   ` Shannon Sterz [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=DCIBA8J3USHP.G8NMJFOM7I59@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=pve-devel-bounces@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal