From: "Peter T. Breuer" <ptb@inv.it.uc3m.es>
To: "Lion Vollnhals" <lion.vollnhals@web.de>
Cc: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: .o.cmd files wanted, static analysis
Date: Fri, 16 Sep 2005 20:39:48 +0200 (MET DST) [thread overview]
Message-ID: <200509161839.j8GIdm818530@inv.it.uc3m.es> (raw)
In-Reply-To: <200509161502.17861.lion.vollnhals@web.de> from "Lion Vollnhals" at "Sep 16, 2005 03:02:17 pm"
"Also sprach Lion Vollnhals:"
> Hi!
>
> Here are mine *.o.cmd files.
Thanks! I should be able to work with that.
Peter
next parent reply other threads:[~2005-09-16 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509161502.17861.lion.vollnhals@web.de>
2005-09-16 18:39 ` Peter T. Breuer [this message]
[not found] <432B332F.8070808@tuxrocks.com>
2005-09-17 4:25 ` Peter T. Breuer
2005-09-15 23:50 Peter T. Breuer
2005-09-16 0:08 ` Kyle Moffett
2005-09-16 6:46 ` Peter T. Breuer
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=200509161839.j8GIdm818530@inv.it.uc3m.es \
--to=ptb@inv.it.uc3m.es \
--cc=linux-kernel@vger.kernel.org \
--cc=lion.vollnhals@web.de \
/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
all inboxes | Powered by JetHome®