From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: CI on own fork always fails because the branch is out of date albeit it isn't
Date: Sat, 31 Dec 2022 15:43:58 +0100 [thread overview]
Message-ID: <20221231144358.0I5i-727XATsitJD2P-xuDWUV2ZCkYK6Ag-ttLsXgVc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41376@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
New comment by steinex on void-packages repository
https://github.com/void-linux/void-packages/issues/41376#issuecomment-1368224563
Comment:
Yes, the master branch of my fork is up-to date. The script you mention gives nothing besides
```
Changed packages:
```
So I assume that means there are no changed between my fork and master.
next prev parent reply other threads:[~2022-12-31 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 10:53 [ISSUE] " steinex
2022-12-31 14:20 ` classabbyamp
2022-12-31 14:43 ` steinex
2022-12-31 14:43 ` steinex [this message]
2022-12-31 14:44 ` steinex
2022-12-31 14:49 ` classabbyamp
2023-01-04 22:10 ` Chocimier
2023-01-07 12:51 ` classabbyamp
2023-01-08 18:59 ` steinex
2023-01-10 23:07 ` [ISSUE] [CLOSED] " 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=20221231144358.0I5i-727XATsitJD2P-xuDWUV2ZCkYK6Ag-ttLsXgVc@z \
--to=steinex@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).