From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] onc-rpc-devel-2_19_20140211-1
Date: Thu, 27 Mar 2014 15:37:00 -0000 [thread overview]
Message-ID: <20140327153728.GU27624@calimero.vinschen.de> (raw)
In-Reply-To: <20140327145556.GA2891@ednor.casa.cgf.cx>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Mar 27 10:55, Christopher Faylor wrote:
> On Thu, Mar 27, 2014 at 10:02:37AM +0100, Corinna Vinschen wrote:
> >On Mar 24 17:14, Pavel Fedin wrote:
> >> Hello!
> >>
> >> > So why
> >> > not just provide a single onc-rpc-devel, that should be entirely
> >> > sufficent.
> >>
> >> onc-rpc-headers is obsolete, ignore it. The idea of creating onc-rpc-devel came to me in order to merge headers and rpcgen.
> >
> >Did you send your ssh key per
> >
> > https://sourceware.org/cygwin-apps/package-upload.html
> >
> >already?
>
> It won't do any good until he's in cygwin-pkg-maint.
Done. Btw., it just occured to me that the version numeber of the
package is using underscores instead of dots. That should be
onc-rpc-devel-2.19.20140211-1 shouldn't it?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-03-27 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 11:48 Pavel Fedin
2014-03-24 9:41 ` Corinna Vinschen
2014-03-24 13:14 ` Pavel Fedin
2014-03-27 9:02 ` Corinna Vinschen
2014-03-27 14:56 ` Christopher Faylor
2014-03-27 15:37 ` Corinna Vinschen [this message]
2014-03-31 5:52 ` Pavel Fedin
-- strict thread matches above, loose matches on Subject: below --
2014-02-12 12:45 Pavel Fedin
2014-02-12 17:04 ` Charles Wilson
2014-02-13 5:24 ` Pavel Fedin
2014-02-19 5:26 ` Pavel Fedin
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=20140327153728.GU27624@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).