From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [Attn Maintainer] git git-svn
Date: Sat, 01 Aug 2015 14:18:00 -0000 [thread overview]
Message-ID: <55BCD544.9080800@dronecode.org.uk> (raw)
In-Reply-To: <87vbd1h1qb.fsf@Rainer.invalid>
On 30/07/2015 20:41, Achim Gratz wrote:
> Adam Dinwoodie writes:
>> These packages are now uploaded, with a "!perl" file instead of a
>> "!ready" file.
>
> Thanks.
>
>> I'm going to look at taking the latest upstream releases once the new
>> version of Perl has been released; I didn't want to take a version bump
>> while we are also taking other changes.
I think git-svn should and used to depend on subversion-perl, but this
seems to have gone missing, somehow.
next prev parent reply other threads:[~2015-08-01 14:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 19:45 Achim Gratz
2015-07-27 21:30 ` Adam Dinwoodie
2015-07-28 5:44 ` Achim Gratz
2015-07-30 1:01 ` Adam Dinwoodie
2015-07-30 19:41 ` Achim Gratz
2015-08-01 14:18 ` Jon TURNEY [this message]
2015-08-01 15:26 ` Adam Dinwoodie
2015-08-01 18:18 ` Achim Gratz
2015-08-07 20:46 ` Adam Dinwoodie
2015-08-02 6:35 ` Achim Gratz
2015-08-07 20:50 ` Adam Dinwoodie
2015-08-08 5:38 ` Achim Gratz
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=55BCD544.9080800@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).