From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: ltp-announce@lists.sourceforge.net
Cc: ltp-list@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [ANNOUNCEMENT] New mailing list created for git commits
Date: Mon, 15 Mar 2010 12:15:24 +0530 [thread overview]
Message-ID: <20100315064524.GA3537@linux.vnet.ibm.com> (raw)
Hi All,
Previosuly we had ltp-cvs@lists.sourceforge.net , intended for capturing all the
history for cvs commits we do. But not for git commits history it is something
which does not suits.
So i have created one new mailing list name as
(ltp-commits@lists.sourceforge.net) suggested by Garret. Thanks.
>From now onwards all the git commit message will go to this mailing list.
You can subscribe through the web page:
https://lists.sourceforge.net/lists/listinfo/ltp-commits
Also few other attention i want to give on importance of mailing list usage
which is currently with LTP project on sf.net.
ltp-list :
- This mailing list is only for sending patches and carry forward all
discussion about patches and features.
ltp-results:
- Maintainer or someone can send the log/results if they want to share on
certain build.
ltp-announcement:
- All the announcement will made here, similar like this email.
ltp-coverage:
- Contains all the code coverage related data/mails/patches.
So i would recommend every users who usage ltp atleast once to subscribe these
lists for there upto date.
As usual i am always open for any suggestions/inputs to make LTP better.
--
Thanks & Regards
Rishi
LTP Maintainer
IBM, LTC, Bangalore
Please join IRC #ltp @ irc.freenode.net
next reply other threads:[~2010-03-15 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 6:45 Rishikesh K Rajak [this message]
2010-03-21 10:10 ` [ANNOUNCEMENT] New mailing list created for git commits Jon Masters
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=20100315064524.GA3537@linux.vnet.ibm.com \
--to=risrajak@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-announce@lists.sourceforge.net \
--cc=ltp-list@lists.sourceforge.net \
/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