From: Christoph Heiss <c.heiss@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-{api, gui, docs, log-tracker} 0/4] add .gitignore files for dpkg build artifacts
Date: Mon, 30 Sep 2024 17:25:00 +0200 [thread overview]
Message-ID: <20240930152505.1988268-1-c.heiss@proxmox.com> (raw)
As it says on the tin; adds .gitignore rules for the four repos for
ignoring the various files produced during a `make deb` - just a small
dev UX improvement. Same (rules) as we have pretty much elsewhere.
No actual functional changes.
diffstat
========
pmg-api:
Christoph Heiss (1):
gitignore: add rules for dpkg build artifacts
.gitignore | 4 ++++
1 file changed, 4 insertions(+)
create mode 100644 .gitignore
pmg-gui:
Christoph Heiss (1):
gitignore: add rules for dpkg build artifacts
.gitignore | 4 ++++
1 file changed, 4 insertions(+)
create mode 100644 .gitignore
pmg-docs:
Christoph Heiss (1):
gitignore: add rules for dpkg build artifacts
.gitignore | 4 ++++
1 file changed, 4 insertions(+)
pmg-log-tracker:
Christoph Heiss (1):
gitignore: add rules for dpkg build artifacts
.gitignore | 6 ++++++
1 file changed, 6 insertions(+)
--
2.46.0
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
next reply other threads:[~2024-09-30 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 15:25 Christoph Heiss [this message]
2024-09-30 15:25 ` [pmg-devel] [PATCH pmg-api 1/4] gitignore: add rules " Christoph Heiss
2024-09-30 15:25 ` [pmg-devel] [PATCH pmg-gui 2/4] " Christoph Heiss
2024-09-30 15:25 ` [pmg-devel] [PATCH pmg-docs 3/4] " Christoph Heiss
2024-09-30 15:25 ` [pmg-devel] [PATCH pmg-log-tracker 4/4] " Christoph Heiss
2024-10-03 15:07 ` [pmg-devel] applied-series: [PATCH pmg-{api, gui, docs, log-tracker} 0/4] add .gitignore files " Stoiko Ivanov
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=20240930152505.1988268-1-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pmg-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.