From: melroy89 <melroy89@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: winegui-2.5.0
Date: Mon, 01 Jul 2024 17:34:14 +0200 [thread overview]
Message-ID: <20240701153414.B87A52806A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48658@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
New comment by melroy89 on void-packages repository
https://github.com/void-linux/void-packages/pull/48658#issuecomment-2200474097
Comment:
> Commits should be squashed and follow the commit message style:
>
> ```
> New package: <pkgname>-<version>
> ```
>
> https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#committing-your-changes
Yeah that is how I started in February. I try to keep the template up to date, and forget to keep applying those commit message requirements over the past months..
I fixed it now. It's again 1 commit.
next prev parent reply other threads:[~2024-07-01 15:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 19:27 [PR PATCH] New package: winegui-2.3.6 melroy89
2024-02-11 19:29 ` [PR PATCH] [Updated] " melroy89
2024-02-11 20:13 ` melroy89
2024-02-13 0:50 ` [PR PATCH] [Updated] New package: winegui-2.4.0 melroy89
2024-02-13 15:40 ` melroy89
2024-02-19 22:13 ` New package: winegui-2.4.1 melroy89
2024-02-21 1:59 ` [PR PATCH] [Updated] " melroy89
2024-03-04 22:22 ` New package: winegui-2.4.2 melroy89
2024-05-21 18:46 ` [PR PATCH] [Updated] New package: winegui-2.4.3 melroy89
2024-06-22 14:50 ` [PR PATCH] [Updated] New package: winegui-2.5.0 melroy89
2024-06-22 14:50 ` melroy89
2024-06-22 14:53 ` [PR PATCH] [Updated] " melroy89
2024-07-01 15:12 ` Duncaen
2024-07-01 15:34 ` [PR PATCH] [Updated] " melroy89
2024-07-01 15:34 ` melroy89 [this message]
2024-07-01 15:49 ` [PR PATCH] [Merged]: " Duncaen
2024-07-01 15:50 ` melroy89
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=20240701153414.B87A52806A@inbox.vuxu.org \
--to=melroy89@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).