From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: cygport: 'announce' feature branch
Date: Tue, 03 Nov 2015 23:23:00 -0000 [thread overview]
Message-ID: <563941D9.6080606@cornell.edu> (raw)
In-Reply-To: <1446537985.10444.84.camel@cygwin.com>
On 11/3/2015 3:06 AM, Yaakov Selkowitz wrote:
> I just created a new 'announce' feature branch in cygport git:
>
> https://github.com/cygwinports/cygport/tree/announce
>
> The new 'announce' command generates an announcement template from
> the .cygport file based on NAME/VERSION/RELEASE, PKG_NAMES, and
> DESCRIPTION, to which you can easily add release-specific information,
> and then sends the message via an SMTP server. Note that this adds
This is a nice feature. Thanks.
> dependencies on perl-Authen-SASL, perl-MIME-tools, and
perl-MIME-tools isn't in the distro yet. Achim?
> perl-Net-SMTP-SSL, and requires several new SMTP_* configuration options
> in cygport.conf.
>
> Feedback and patches welcome.
If there's no mailserver configured, I'd like to see cygport save the
mbox file in the current directory and give an informational message,
rather than saving it in /tmp and giving an error message. Users might
want to simply paste it into an email, and the error message seems a
little unfriendly.
Ken
P.S. You still haven't applied the texlive patch from
https://cygwin.com/ml/cygwin-apps/2015-08/msg00019.html; is this just an
oversight, or do you need me to explain in more detail why it's needed?
next prev parent reply other threads:[~2015-11-03 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 8:06 Yaakov Selkowitz
2015-11-03 8:57 ` Corinna Vinschen
2015-11-03 16:01 ` Yaakov Selkowitz
2015-11-03 23:23 ` Ken Brown [this message]
2015-11-04 0:10 ` Yaakov Selkowitz
2015-11-04 9:03 ` Corinna Vinschen
2015-11-04 16:12 ` Ken Brown
2015-11-15 21:32 ` Ken Brown
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=563941D9.6080606@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).