From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Lendl <s.lendl@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server] gitignore
Date: Fri, 17 Nov 2023 15:53:12 +0100 [thread overview]
Message-ID: <b97de20c-b334-4106-a700-d9c5aa0b19ee@proxmox.com> (raw)
In-Reply-To: <20231117142025.3323139-2-s.lendl@proxmox.com>
Am 17/11/2023 um 15:20 schrieb Stefan Lendl:
> build output and .vscode
>
> Signed-off-by: Stefan Lendl <s.lendl@proxmox.com>
> ---
> .gitignore | 2 ++
> 1 file changed, 2 insertions(+)
>
>
applied, with the build-dir made slightly more specific by using
/qemu-server-[0-9]*/ and the subject changed to something meaningful than
just a single word (would have been only the second commit consisting of
only one word in the subject), as gitignore, especially if one exists
already, is really not helpful when scrolling e.g., git log --oneline
prev parent reply other threads:[~2023-11-17 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:20 [pve-devel] " Stefan Lendl
2023-11-17 14:53 ` Thomas Lamprecht [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=b97de20c-b334-4106-a700-d9c5aa0b19ee@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.lendl@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