From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] procps
Date: Wed, 16 Mar 2016 10:06:00 -0000 [thread overview]
Message-ID: <20160316100627.GD15577@calimero.vinschen.de> (raw)
In-Reply-To: <20160316093336.GA15577@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]
On Mar 16 10:33, Corinna Vinschen wrote:
> On Mar 16 00:14, Wayne Porter wrote:
> >
> > On March 15, 2016 11:52:35 PM PDT, Achim Gratz <Stromeko@nexgo.de> wrote:
> > >Wayne Porter writes:
> > >> I have just finished porting procps 3.3.9 and wanted to share it with
> > >> the community.
> > >
> > >That's actually procps-ng or is it not? If so, it seems the current
> > >version is 3.3.11 from looking at my Linux box.
> > >
> > >Also, the current procps maintainer is quite active on the Cygwin ml,
> > >so
> > >it would have been a good idea to ask for an update first before doing
> > >an ITA. :-)
> > >
> > >
> > >Regards,
> > >Achim.
> >
> > I'm new to this community so I wasn't sure if I went about this the
> > proper way. 3.3.11 is the latest but is not listed as stable in the
> > debian package list. I was going by the guidelines on the contribution
> > page that for it to be considered for the repos that it has to be.
>
> Don't worry about that for now. As the others pointed out, I'm the
> current procps maintainer. I have no problems to give up procps
> maintainership, but I don't think this is necessary here in the first
> place.
>
> The reason is: Your package is in fact procps-ng, and from my POV it
> should stick to this name as in various Linux distros. My procps code
> is from the older codebase. I never felt a good reason to port the
s/reason/motivation/
Yeah, that's better.
> newer procps-ng codebase to Cygwin, so this is a welcome package.
>
> I happily give up procps in favor of procps-ng, as long as it works as
> desired.
>
> So, please go ahead with your ITP per the other maintainers request.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-16 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 23:02 Wayne Porter
2016-03-16 6:52 ` Achim Gratz
2016-03-16 7:14 ` Wayne Porter
2016-03-16 7:35 ` Marco Atzeri
2016-03-16 7:42 ` Wayne Porter
2016-03-16 7:51 ` Marco Atzeri
2016-03-16 9:33 ` Corinna Vinschen
2016-03-16 10:06 ` Corinna Vinschen [this message]
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=20160316100627.GD15577@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).