From: Sam Ravnborg <sam@ravnborg.org>
To: Karim Yaghmour <karim@opersys.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
LTT-Dev <ltt-dev@shafik.org>
Subject: Re: [PATCH 1/8 ] ltt for 2.6.10: core implementation
Date: Fri, 14 Jan 2005 21:52:42 +0100 [thread overview]
Message-ID: <20050114205242.GC8385@mars.ravnborg.org> (raw)
In-Reply-To: <41E76271.3000004@opersys.com>
Hi Karim.
> + * (C) Copyright, 1999, 2000, 2001, 2002, 2003, 2004 -
> + * Karim Yaghmour (karim@opersys.com)
2005?
> + * Changelog:
> + * 14/12/04, Renamed trace macros and variables to avoid namespace
> + * pollution (i.e. TRACE_XXX is now ltt_ev_xxx, etc.)
...
Common practice is not to include Changelog in files.
Sam
prev parent reply other threads:[~2005-01-14 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 6:10 Karim Yaghmour
2005-01-14 20:52 ` Sam Ravnborg [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=20050114205242.GC8385@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
/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
Powered by JetHome