From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Sichert <l.sichert@proxmox.com>
Subject: applied: [PATCH storage] gitignore: add build artifacts to .gitignore
Date: Sun, 19 Apr 2026 23:47:24 +0200 [thread overview]
Message-ID: <177663524252.4124619.3261485829800271902.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260416152407.70690-1-l.sichert@proxmox.com>
On Thu, 16 Apr 2026 17:24:04 +0200, Lukas Sichert wrote:
> In contrast to other repositories, the build directory as well as
> `.buildinfo` and `.changes` files are currently not ignored by Git.
>
> Add corresponding patterns to `.gitignore` to ignore them.
>
>
Applied, thanks!
[1/1] gitignore: add build artifacts to .gitignore
commit: a4f99a5f64d1f83c839d3779f2016529efa326ee
prev parent reply other threads:[~2026-04-19 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 15:24 Lukas Sichert
2026-04-19 21:47 ` 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=177663524252.4124619.3261485829800271902.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.sichert@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