From: reback00 <reback00@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: goocanvas: update to 3.0.0
Date: Fri, 28 May 2021 12:55:58 +0200 [thread overview]
Message-ID: <20210528105558.jOQiXjj_45Ahad88uEQcm0ZlZ_90NHfaYpZiKmsvnFE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31159@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
New comment by reback00 on void-packages repository
https://github.com/void-linux/void-packages/pull/31159#issuecomment-850334791
Comment:
If the changes are ok, should this PR contain all the changes for updating to goocanvas 3? Or can the changes be in separate PRs for separate packages?
In any case, let me know if I can help in anything.
next prev parent reply other threads:[~2021-05-28 10:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 4:30 [PR PATCH] " reback00
2021-05-28 4:50 ` reback00
2021-05-28 7:03 ` newbluemoon
2021-05-28 10:50 ` reback00
2021-05-28 10:55 ` reback00 [this message]
2021-05-28 10:56 ` reback00
2021-05-28 12:17 ` newbluemoon
2021-05-28 12:56 ` newbluemoon
2021-05-28 13:03 ` newbluemoon
2021-05-28 13:13 ` newbluemoon
2021-05-28 13:25 ` newbluemoon
2021-05-28 17:17 ` [PR PATCH] [Updated] " reback00
2021-05-28 17:24 ` reback00
2021-05-28 17:31 ` newbluemoon
2021-05-28 17:37 ` reback00
2021-05-28 17:50 ` newbluemoon
2021-05-28 17:50 ` reback00
2021-05-28 17:55 ` [PR PATCH] [Updated] " reback00
2021-05-28 18:09 ` reback00
2021-05-28 18:16 ` reback00
2022-05-20 2:12 ` github-actions
2022-06-04 2:08 ` [PR PATCH] [Closed]: " github-actions
2022-10-03 1:36 [PR PATCH] " Wesley-Chan
2022-10-03 9:38 ` Wesley-Chan
2022-10-03 11:10 ` classabbyamp
2022-10-03 13:24 ` classabbyamp
2022-10-03 13:24 ` classabbyamp
2022-10-03 13:35 ` Wesley-Chan
2022-10-03 13:47 ` classabbyamp
2023-01-02 1:57 ` github-actions
2023-01-02 5:31 ` newbluemoon
2023-04-04 1:53 ` github-actions
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=20210528105558.jOQiXjj_45Ahad88uEQcm0ZlZ_90NHfaYpZiKmsvnFE@z \
--to=reback00@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).