From: MIvanchev <MIvanchev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: fritzing
Date: Sat, 30 Mar 2024 10:41:42 +0100 [thread overview]
Message-ID: <20240330094142.D43BB24A64@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49544@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
New comment by MIvanchev on void-packages repository
https://github.com/void-linux/void-packages/issues/49544#issuecomment-2027993666
Comment:
I see, well that's a very odd thing so maybe we should wait until they actually tag something again. To prevent someone releasing 1.x.y a couple of times. for example.
next prev parent reply other threads:[~2024-03-30 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 7:46 [ISSUE] " U2C9727A4
2024-03-30 9:29 ` MIvanchev
2024-03-30 9:34 ` classabbyamp
2024-03-30 9:41 ` MIvanchev [this message]
2024-04-08 8:43 ` 0x5c
2024-06-14 7:15 ` [ISSUE] [CLOSED] " classabbyamp
2024-06-14 7:15 ` classabbyamp
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=20240330094142.D43BB24A64@inbox.vuxu.org \
--to=mivanchev@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).