From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Cc: Jiri Palecek <jpalecek@web.de>
Subject: Re: [LTP] [PATCH] Other compiler warning fixes
Date: Fri, 30 Oct 2009 17:21:44 -0400 [thread overview]
Message-ID: <200910301721.44934.vapier@gentoo.org> (raw)
In-Reply-To: <4aeb19e8.8c13f30a.0cad.ffffd3c6SMTPIN_ADDED@mx.google.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 231 bytes --]
On Wednesday 21 October 2009 15:37:32 Jiri Palecek wrote:
> Hello,
something seems to be screwed up on your end. all of your patches keep coming
across with dates set to like 9 days ago. can you please check that ?
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 399 bytes --]
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next parent reply other threads:[~2009-10-30 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4aeb19e8.8c13f30a.0cad.ffffd3c6SMTPIN_ADDED@mx.google.com>
2009-10-30 21:21 ` Mike Frysinger [this message]
[not found] <200910301649.n9UGnbHJ001240@e34.co.us.ibm.com>
2009-11-02 13:59 ` [LTP] [PATCH] Other compiler warning fixes Subrata Modak
2009-10-21 19:37 Jiri Palecek
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=200910301721.44934.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=jpalecek@web.de \
--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