public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Federico Kircheis <federico.kircheis@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] neomutt
Date: Wed, 31 Jan 2018 19:21:00 -0000	[thread overview]
Message-ID: <fedd8536-09b6-eba0-4967-47c6de625b42@gmail.com> (raw)
In-Reply-To: <8efecd3c-1809-4ab4-d027-f3e959a46a7c@dronecode.org.uk>



On 01/31/2018 06:55 PM, Jon Turney wrote:
> On 30/01/2018 05:56, Federico Kircheis wrote:
>> On 01/28/2018 03:43 PM, Jon Turney wrote:
>>> On 28/01/2018 11:38, Federico Kircheis wrote:
>>>> Name: Federico Kircheis
>>>> Package: neomutt
>>>
>>> Done
>>
>> Uploaded.
> 
> Please upload a x86 package as well.
> 

I'm sorry, I uploaded it, too.

I thought that the previous upload would have been valid both for x64 
and x86.

I was unsure how to proceed, so I've downloaded a x86 version of cygwin, 
copied the cygport file in a separate directory, and so on.

Is there a way to update the package for x64 and x86 at once?
Without using ftp directly of course.

`man cygport` mentions the `--32` and `--64` parameters for building the 
package, but not for uploading it and I did not want to try it out 
before messing something up on the server :-)


Federico

  reply	other threads:[~2018-01-31 19:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-20  7:43 Federico Kircheis
2018-01-20 18:22 ` Marco Atzeri
2018-01-20 19:52   ` Federico Kircheis
2018-01-21 17:51     ` Jon Turney
2018-01-21 20:18       ` Federico Kircheis
2018-01-24 18:07         ` Federico Kircheis
2018-01-26 17:01           ` Jon Turney
2018-01-28 11:38             ` Federico Kircheis
2018-01-28 14:43               ` Jon Turney
2018-01-30  5:56                 ` Federico Kircheis
2018-01-31 17:55                   ` Jon Turney
2018-01-31 19:21                     ` Federico Kircheis [this message]
2018-02-02 19:24                       ` Jon Turney

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=fedd8536-09b6-eba0-4967-47c6de625b42@gmail.com \
    --to=federico.kircheis@gmail.com \
    --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).