public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Marco Atzeri via Cygwin-announce <cygwin-announce@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: guile-3.0.9-2
Date: Thu, 1 Jun 2023 01:45:18 +0000 (UTC)	[thread overview]
Message-ID: <1655626221.2764790.1685583918500@mail.yahoo.com> (raw)
In-Reply-To: <announce.f89e6fde-93ed-792c-4f64-2de8c65e5489@gmail.com>

On Saturday, May 13, 2023 at 11:40:01 PM PDT, Marco Atzeri via Cygwin-announce via Cygwin <cygwin@cygwin.com> wrote: 

> Version 3.0.9-2 of

>   guile3.0
>   libguile3.0-devel
>   libguile3.0_1

> have been uploaded for cygwin.

Hello Marco and Cygwin:

Where can I find the source patches that Cygwin uses for guile3.0?

On Github, for some project, I'm trying to make my own
CI/CD nightly build of upstream Guile's main branch on a
handful of OSs, and I'm having a bit of trouble getting Cygwin
to build.

If anyone's curious, here's my Github Action YML so far.

https://github.com/spk121/guile/blob/main-patches/.github/workflows/windows-cygwin.yml

Regards,
Mike Gran

           reply	other threads:[~2023-06-01  1:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <announce.f89e6fde-93ed-792c-4f64-2de8c65e5489@gmail.com>]

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=1655626221.2764790.1685583918500@mail.yahoo.com \
    --to=spk121@yahoo.com \
    --cc=cygwin-announce@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).