From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] xdg-desktop-portal-gnome: update to 43.0.
Date: Sun, 02 Oct 2022 03:27:24 +0200 [thread overview]
Message-ID: <20221002012724.9REbx_kl2vnSuD_3yC0fa9HC5pgc6Sa3kKSJokx2ojo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39521@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
New review comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/39521#discussion_r985164298
Comment:
> the default branch is main, not master
Thanks.
> the changelog should be pulled from that branch, not the branch associated with a certain release
It's commented out, the changlogs for specific branches are stored in that branch, when xdg-desktop-portal-gnome's main branch is gnome 44 and patches need to be backported for gnome 43, the changelogs for those patch releases won't appear in main usually.
Hence why you don't see any change information for 42.1, 42.2, and 42.3 in the changelog in the main branch (those are only in the gnome-42 branch).
next prev parent reply other threads:[~2022-10-02 1:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 3:48 [PR PATCH] " oreo639
2022-10-02 1:06 ` [PR PATCH] [Updated] " oreo639
2022-10-02 1:16 ` [PR REVIEW] " classabbyamp
2022-10-02 1:18 ` [PR PATCH] [Updated] " oreo639
2022-10-02 1:21 ` [PR REVIEW] " classabbyamp
2022-10-02 1:23 ` [PR PATCH] [Updated] " oreo639
2022-10-02 1:26 ` [PR REVIEW] " oreo639
2022-10-02 1:26 ` oreo639
2022-10-02 1:27 ` oreo639 [this message]
2022-10-02 1:28 ` classabbyamp
2022-10-02 1:33 ` [PR PATCH] [Updated] " oreo639
2022-10-02 1:33 ` oreo639
2022-10-02 1:38 ` [PR PATCH] [Merged]: " 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=20221002012724.9REbx_kl2vnSuD_3yC0fa9HC5pgc6Sa3kKSJokx2ojo@z \
--to=oreo639@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).