From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [RFC]: multiple entries in $changelog
Date: Mon, 13 Mar 2023 09:08:31 +0100 [thread overview]
Message-ID: <20230313080831._NMoqwJ-QAECjO-1SKTKbdHTPCJTwz1EOhcFIeMt7RU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36387@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
Closed issue by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/36387
Description:
Some projects have two sources for $changelog - one from the master/main branch for rcs, alphas, betas and first releases in a series and one from a maintenance branch for patch releases. This is mostly visible in GNOME projects, but other projects also use this strategy.
Sometimes the maintenance branch doesn't exist until it's needed which means that if we decide to use the maintenance branch for the changelog, it will be a 404 link until they create the branch (#36353).
This can be solved with allowing multiple entries in the $changelog field.
prev parent reply other threads:[~2023-03-13 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 21:59 [ISSUE] " paper42
2022-03-30 3:09 ` classabbyamp
2022-03-30 3:09 ` classabbyamp
2022-04-09 12:27 ` Anachron
2022-07-09 2:13 ` github-actions
2022-10-08 2:13 ` github-actions
2022-10-08 2:18 ` classabbyamp
2022-10-08 2:18 ` classabbyamp
2022-12-12 6:47 ` paper42
2023-03-13 1:58 ` github-actions
2023-03-13 8:08 ` paper42 [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=20230313080831._NMoqwJ-QAECjO-1SKTKbdHTPCJTwz1EOhcFIeMt7RU@z \
--to=paper42@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).