public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Request package updates for Poppler, Subversion and Git
Date: Fri, 10 Jan 2020 19:55:00 -0000	[thread overview]
Message-ID: <CA+kUOamm7moRMBAurA8kdxMjqFZo4oyrjHc7OOYa9nXmumj9Bg@mail.gmail.com> (raw)
In-Reply-To: <qtoada$7sbr$1@blaine.gmane.org>

Hi Achim,

On Sun, 22 Dec 2019 at 17:50, Achim Gratz wrote:
>
> Am 22.12.2019 um 13:50 schrieb Adam Dinwoodie:
> > Acknowledged for Git. I'll try and get a new release out before the new year.
>
> Keep in mind you will then have to re-do it just after the new year for
> the Perl update.

Just realised I hadn't replied to this, sorry!

On the apps list, on the topic of package updates for the Perl switch, you said

> Git isn't affected because it sets up @INC itself and doesn't have
> architecture-specific modules.

I'd therefore been assuming that I didn't need to worry about syncing
a Git release with the Perl update; have I misunderstood what's going
on here?

Adam

PS: I am once again battling a bunch of test failures, as I prefer to
not release a Git build with undiagnosed failures in the test suite
when it's the official Cygwin distribution. I'm slowly working my way
through the problems, but there is ongoing progress on getting a new
release out.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2020-01-10 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 16:26 Kptain
2019-12-20 16:29 ` Marco Atzeri
2019-12-21  2:45   ` Steven Penny
2019-12-22 14:05 ` Adam Dinwoodie
2019-12-22 21:20   ` Achim Gratz
2019-12-23  3:17     ` Steven Penny
2020-01-10 19:55     ` Adam Dinwoodie [this message]
2020-01-10 20:33       ` Achim Gratz
2020-01-13 10:36         ` Kptain
2020-04-11 19:43       ` majeed
2020-04-12 13:17 Steven Penny
2020-04-12 17:27 ` Z. Majeed

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=CA+kUOamm7moRMBAurA8kdxMjqFZo4oyrjHc7OOYa9nXmumj9Bg@mail.gmail.com \
    --to=adam@dinwoodie.org \
    --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).