Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: backintime: update to 1.4.3.
Date: Tue, 11 Jun 2024 22:04:44 +0200	[thread overview]
Message-ID: <20240611200445.054322B509@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47880@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

There's a merged pull request on the void-packages repository

backintime: update to 1.4.3.
https://github.com/void-linux/void-packages/pull/47880

Description:
#### Testing the changes
- I tested the changes in this PR: **YES**. The Qt GUI launches and I can setup backup targets. The CLI runs and doesn't complain, but I don't know how to use it so I assume it's fine also.

#### Local build testing
- I built this PR locally for my native architecture, `x86_64-glibc`

#### Questions to maintainers
- The package revision has been reset to `1`, because the minor version changed to `4`. Please tell me if this is correct.

#### Further Notes
- The patch `srcpkgs/backintime/patches/e1ae23ddc0b4229053e3e9c6c61adcb7f3d8e9b3.patch` has been deleted because it is included in backintime 1.4.1 (see https://github.com/bit-team/backintime/commit/e1ae23ddc0b4229053e3e9c6c61adcb7f3d8e9b3).

      parent reply	other threads:[~2024-06-11 20:04 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 23:28 [PR PATCH] backintime: update to 1.4.1 thetredev
2023-12-22 23:38 ` Duncaen
2023-12-22 23:47 ` thetredev
2023-12-23  0:01 ` [PR PATCH] [Updated] " thetredev
2023-12-23  0:01 ` thetredev
2023-12-23  0:03 ` thetredev
2023-12-23  0:04 ` thetredev
2023-12-23  0:06 ` [PR REVIEW] " Duncaen
2023-12-23  0:17 ` thetredev
2023-12-23  0:30 ` thetredev
2023-12-23  0:30 ` thetredev
2023-12-23  0:31 ` thetredev
2023-12-23  0:33 ` thetredev
2023-12-23  0:34 ` thetredev
2023-12-23  0:37 ` thetredev
2023-12-23  0:40 ` thetredev
2023-12-23  0:46 ` Duncaen
2023-12-23  0:50 ` thetredev
2023-12-23  0:50 ` thetredev
2023-12-23  0:55 ` [PR PATCH] [Updated] " thetredev
2023-12-23  0:55 ` [PR REVIEW] " thetredev
2023-12-23 16:54 ` classabbyamp
2023-12-23 16:57 ` classabbyamp
2023-12-23 16:58 ` classabbyamp
2023-12-23 18:59 ` thetredev
2023-12-23 19:26 ` classabbyamp
2023-12-23 19:27 ` thetredev
2024-03-09 23:14 ` [PR PATCH] [Updated] " thetredev
2024-03-09 23:14 ` backintime: update to 1.4.3 thetredev
2024-03-09 23:17 ` [PR REVIEW] " thetredev
2024-03-09 23:18 ` [PR PATCH] [Updated] " thetredev
2024-03-09 23:21 ` thetredev
2024-03-09 23:21 ` thetredev
2024-03-11  0:01 ` [PR REVIEW] " classabbyamp
2024-03-11  0:07 ` thetredev
2024-03-11  0:09 ` thetredev
2024-03-11  0:12 ` classabbyamp
2024-03-11  0:15 ` thetredev
2024-03-11  0:16 ` [PR PATCH] [Updated] " thetredev
2024-03-11  0:19 ` [PR REVIEW] " thetredev
2024-03-11  0:19 ` thetredev
2024-03-11  0:24 ` [PR PATCH] [Updated] " thetredev
2024-03-11  0:26 ` thetredev
2024-03-11  0:28 ` [PR PATCH] [Updated] " thetredev
2024-03-11  0:29 ` thetredev
2024-03-11  0:39 ` [PR PATCH] [Updated] " thetredev
2024-03-11  0:40 ` thetredev
2024-06-09  1:52 ` github-actions
2024-06-11 19:57 ` [PR PATCH] [Updated] " thetredev
2024-06-11 19:57 ` thetredev
2024-06-11 20:04 ` classabbyamp [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=20240611200445.054322B509@inbox.vuxu.org \
    --to=classabbyamp@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).