From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] Fix for some warnings
Date: Fri, 11 Jan 2008 11:09:12 +0000 [thread overview]
Message-ID: <1200049520-sup-6114@tomsk> (raw)
This patch fixes a couple of warnings in message and message-chunks.
The first is because a log message uses the from address before it is
assigned, the second is because @lines is uninitialised in some cases
(a sourceforge message in my case that didnt have any text content)
This stops the console getting filled with warnings on spam.
Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: warnings-patch
Type: application/octet-stream
Size: 1668 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080111/07581dd7/attachment.obj
next reply other threads:[~2008-01-11 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 11:09 Marcus Williams [this message]
2008-01-13 2:32 ` William Morgan
2008-01-13 3:32 ` William Morgan
2008-01-14 2:17 ` William Morgan
2008-01-13 18:19 ` Marcus Williams
2008-01-15 14:02 ` [sup-talk] [PATCH] Fix for some warnings on faked addresses and ids Marcus Williams
2008-01-16 1:32 ` William Morgan
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=1200049520-sup-6114@tomsk \
--to=marcus-sup@bar-coded.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