From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: two questions about new upload method
Date: Sat, 30 Nov 2013 16:18:00 -0000 [thread overview]
Message-ID: <529A0FA5.50905@cornell.edu> (raw)
In-Reply-To: <rf9j99107e262ho7eokutlhdgo9c4861qh@4ax.com>
On 11/30/2013 3:47 AM, Andrew Schulman wrote:
>> On Fri, Nov 29, 2013 at 10:06:50PM -0500, Christopher Faylor wrote:
>>> On Fri, Nov 29, 2013 at 01:13:30PM -0500, Christopher Faylor wrote:
>>>> I added you as the owner for "unison" and "unison2.45".
>>>
>>> Which didn't do anything. I'm investigating why now.
>>
>> It was because the !ready files disappeared after the previous
>> run. I put one in unison/unison2.45 and the files were moved.
>
> Thanks. The packages are out now.
I see unison2.45 but not the others.
Ken
next prev parent reply other threads:[~2013-11-30 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 17:27 Andrew Schulman
2013-11-29 18:13 ` Christopher Faylor
2013-11-30 3:07 ` Christopher Faylor
2013-11-30 4:46 ` Christopher Faylor
2013-11-30 8:48 ` Andrew Schulman
2013-11-30 16:18 ` Ken Brown [this message]
2013-11-30 17:48 ` Andrew Schulman
2013-11-30 19:40 ` Christopher Faylor
2013-12-01 9:28 ` Andrew Schulman
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=529A0FA5.50905@cornell.edu \
--to=kbrown@cornell.edu \
--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).