public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001509] Fix compiler warnings about uninitalized variables in inet_ntop6
Date: Sat, 03 Mar 2012 04:00:00 -0000	[thread overview]
Message-ID: <20120303040033.AB6DA2FB082D@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001509-777@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001509

Jonathan Larmour <jifl@ecoscentric.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #1609|                            |assignment+, review+
               Flag|                            |

--- Comment #1 from Jonathan Larmour <jifl@ecoscentric.com> 2012-03-03 04:00:32 GMT ---
(From update of attachment 1609)
This is unfortunate but fine.

I've just noticed in this and the other patches, can you just make sure there's
a blank line between the ChangeLog header and the first line of changes. Just
to follow the standard format and the existing ChangeLog entry formats, thanks.

After that, please check it in.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


  reply	other threads:[~2012-03-03  4:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 22:00 [Bug 1001509] New: " bugzilla-daemon
2012-03-03  4:00 ` bugzilla-daemon [this message]
2012-03-06 19:19 ` [Bug 1001509] " bugzilla-daemon
2012-03-02 22:00 [Bug 1001509] New: " bugzilla-daemon
2012-03-03  4:00 ` [Bug 1001509] " bugzilla-daemon
2012-03-06 19:19 ` bugzilla-daemon

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=20120303040033.AB6DA2FB082D@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=unassigned@bugs.ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).