On 2021-09-22 19:05, Jason Pyeron wrote:
On Wednesday, September 22, 2021 8:44 PM, Brian Inglis wrote:
Your push should do a lazy create of the git repo, and start the
scallywag CI job on Github actions.
In my case, the build requires much older versions of Cygwin to build at the
moment. Wou
> -Original Message-
> From: Brian Inglis
> Sent: Wednesday, September 22, 2021 8:44 PM
snip
>
> Your push should do a lazy create of the git repo, and start the
> scallywag CI job on Github actions.
In my case, the build requires much older versions of Cygwin to build at the
moment. Wou
On 2021-09-22 13:17, Jason Pyeron wrote:
-Original Message-
Changed maintainer
Who has to create the git repo?
I would like to push my postfix cygport and patch files.
Your push should do a lazy create of the git repo, and start the
scallywag CI job on Github actions.
Don't forget t
On 9/20/2021 8:57 AM, Ken Brown via Cygwin-apps wrote:
On 9/20/2021 1:58 AM, ASSI wrote:
Ken Brown via Cygwin-apps writes:
2. Create a script /usr/bin/rebaselst_usr similar to rebaselst, with a
few modifications:
a) All files are in the user's home directory:
l=${HOME}/.config/rebase
b=${HOME
> -Original Message-
> From: Marco Atzeri
> Sent: Monday, September 20, 2021 3:09 PM
>
>
> Changed maintainer
Who has to create the git repo?
I would like to push my postfix cygport and patch files.
v/r,
Jason Pyeron
--
Jason Pyeron | Architect
PD Inc| Certified SBA 8(a)
10
Would this be an acceptable improvement?
I would like my cygport file to capture specific and deviant requirements. E.g.
cannot compile with GCC 10+
The warning emitted is better than relying on a commit message or comment in
the cygport.
$ diff -u usr/share/cygport/lib/check_funcs.cygpart.ori
