From: Leon Romanovsky <leon@leon.nu>
To: ratheesh k <ratheesh.ksz@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Any problem ?
Date: Fri, 28 Jan 2011 22:46:18 +0200 [thread overview]
Message-ID: <AANLkTinHSY3Jd7Th6zmLZCo0ziwCJrMJuQT78t3Nr1_B@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimg=+0jUVjyG2Zq7ZqC=A5XbjWfkjoJADmPsULK@mail.gmail.com>
> str=NULL;
In general, you don't need this line.
--
"Change is inevitable; progress is optional".
next prev parent reply other threads:[~2011-01-28 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 11:53 Any problem ? ratheesh k
2011-01-28 12:02 ` Santosh Sivaraj
[not found] ` <AANLkTimg=+0jUVjyG2Zq7ZqC=A5XbjWfkjoJADmPsULK@mail.gmail.com>
2011-01-28 20:46 ` Leon Romanovsky [this message]
2011-01-28 21:01 ` David Astua
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=AANLkTinHSY3Jd7Th6zmLZCo0ziwCJrMJuQT78t3Nr1_B@mail.gmail.com \
--to=leon@leon.nu \
--cc=linux-c-programming@vger.kernel.org \
--cc=ratheesh.ksz@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;
as well as URLs for NNTP newsgroup(s).