From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Jari Aalto <jari.aalto@cante.net>
Subject: Re: cfget-0.18-1 32bit (uploaded soon)
Date: Thu, 05 Nov 2015 13:12:00 -0000 [thread overview]
Message-ID: <563B55C9.2000002@dronecode.org.uk> (raw)
In-Reply-To: <563B2EF2.9000807@gmail.com>
On 05/11/2015 10:26, Marco Atzeri wrote:
> On 05/11/2015 10:54, Jari Aalto wrote:
>> On 2015-11-05 10:26, Corinna Vinschen wrote:
>> | On Oct 20 12:23, Corinna Vinschen wrote:
>> | > Jari, ping?
>> | >
>> | > On Oct 19 17:54, Marco Atzeri wrote:
>> | > > On 19/10/2015 17:45, Corinna Vinschen wrote:
>> | > > >On Sep 26 11:43, Marco Atzeri wrote:
>> | > > >>Jari,
>> | > > >>any specific reason why there is only a 64 bit version ?
>> | > > >>
>> | > > >>As it seems just a python script, it should work on both arch
>> correct ?
>> | > > >
>> | > > >Did this get resolved?
>> | > > >
>> | > > >
>> | > > >Corinna
>> | > >
>> | > > the 32bit version is still missing
>>
>> Hm, must have slipped through my eyes. I'll take care of it ASAP.
>>
>> Jari
>>
>
> aewm++ 64 bit also, please.
>
> You uploaded only aewm++-goodies
>
> $ grep aewm++ pkg_arch.txt
> aewm++ 32 bit Jari Aalto
> aewm++-goodies Both Jari Aalto
I noticed that aewm++ 1.1.2-2 packages for both x86 and x86_64 have been
sitting in Jari's upload area on sourceware for a while.
I'm not sure if that's because he hasn't marked them ready, or some kind
of upset bug is happening.
next prev parent reply other threads:[~2015-11-05 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 9:43 cfget-0.18-1 32bit ? Marco Atzeri
2015-10-19 15:45 ` Corinna Vinschen
2015-10-19 15:55 ` Marco Atzeri
2015-10-20 10:23 ` Corinna Vinschen
2015-11-05 9:26 ` Corinna Vinschen
2015-11-05 9:54 ` cfget-0.18-1 32bit (uploaded soon) Jari Aalto
2015-11-05 10:27 ` Marco Atzeri
2015-11-05 13:12 ` Jon Turney [this message]
2015-11-05 13:22 ` Marco Atzeri
2015-11-05 21:12 ` cfget-0.18-1 32bit (aewm* uploaded soon) Jari Aalto
2016-02-12 14:22 ` Jon Turney
2016-02-12 17:57 ` Jari Aalto
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=563B55C9.2000002@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=jari.aalto@cante.net \
/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).