From: "Serge E. Hallyn" <serge.hallyn@canonical.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] About Community discussion
Date: Mon, 13 Dec 2010 08:12:46 -0600 [thread overview]
Message-ID: <20101213141246.GB17546@hallyn.com> (raw)
In-Reply-To: <AANLkTim_ExzOr2G-NnzLWB=b14zj8s5c1pYjsZEkine7@mail.gmail.com>
Quoting Garrett Cooper (yanegomi@gmail.com):
> That being said, it still puzzles me why other folks attached to
> the project have been largely silent over the past couple months or
> years (in particular the official maintainers), as I would figure that
> they would have a vested interest in insuring that the changes being
> committed to the project are consistent and/or high quality.
I'd sort of assumed you had taken over maintainership! Is Subrata still
trying to be involved? Does IBM have any resources assigned at all?
-serge
------------------------------------------------------------------------------
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages,
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-12-13 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D058241.7040603@cn.fujitsu.com>
2010-12-13 9:16 ` [LTP] About Community discussion Garrett Cooper
2010-12-13 14:12 ` Serge E. Hallyn [this message]
2010-12-13 16:26 ` Garrett Cooper
2010-12-13 16:48 ` Rajak, Rishikesh Kumar
2010-12-13 17:35 ` Subrata Modak
2010-12-13 17:40 ` Garrett Cooper
2010-12-15 2:04 ` Gui Jianfeng
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=20101213141246.GB17546@hallyn.com \
--to=serge.hallyn@canonical.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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