From: Johannes Sixt <j.sixt@viscovery.net>
To: Frank Li <lznuaa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: possible code error at run_command.c
Date: Mon, 21 Dec 2009 09:30:02 +0100 [thread overview]
Message-ID: <4B2F320A.6010908@viscovery.net> (raw)
In-Reply-To: <1976ea660912210018y15acfe32o78841d5e0968f793@mail.gmail.com>
Frank Li schrieb:
> Maybe some excute path miss initialized it. Otherwise compiler will
> not report warning.
LOOK AT THE CODE. There is no such code path.
-- Hannes
next prev parent reply other threads:[~2009-12-21 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 6:46 possible code error at run_command.c Frank Li
2009-12-21 7:09 ` Wincent Colaiuta
2009-12-21 7:18 ` Johannes Sixt
2009-12-21 7:29 ` Frank Li
2009-12-21 7:43 ` Johannes Sixt
2009-12-21 8:18 ` Frank Li
2009-12-21 8:30 ` Johannes Sixt [this message]
2009-12-21 8:41 ` Erik Faye-Lund
2009-12-21 8:52 ` Johannes Sixt
2009-12-21 9:08 ` Erik Faye-Lund
2009-12-21 9:13 ` Frank Li
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=4B2F320A.6010908@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=lznuaa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.