public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "makhota at gmx dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/1390] localtime call causes Segmentation Fault
Date: Wed, 28 Dec 2005 19:14:00 -0000	[thread overview]
Message-ID: <20051228191435.32680.qmail@sourceware.org> (raw)
In-Reply-To: <20050929005004.1390.makhota@gmx.net>


------- Additional Comments From makhota at gmx dot net  2005-12-28 19:14 -------
Listen, I am not asking to teach me programming. My question is: show me that 
part of standard. I do NOT consider "read the standard" as an argumented 
answer. What I do, however, consider as an answer is something like "paragraph 
xxx from http://xxxx/xxx/xx explains what you need."

Just in case I am still not clear: please, give me a link (URL, page#, 
whatever that helps me find that) to the part of POSIX you are referring to. 

Thank you.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |


http://sourceware.org/bugzilla/show_bug.cgi?id=1390

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2005-12-28 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29  0:51 [Bug libc/1390] New: " makhota at gmx dot net
2005-09-29  8:38 ` [Bug libc/1390] " schwab at suse dot de
2005-09-29 16:01 ` makhota at gmx dot net
2005-09-29 16:02 ` makhota at gmx dot net
2005-10-11  4:25 ` drepper at redhat dot com
2005-11-02 22:18 ` makhota at gmx dot net
2005-12-23  4:05 ` drepper at redhat dot com
2005-12-28 19:14 ` makhota at gmx dot net [this message]
2005-12-29  0:04 ` mark9781 at yahoo dot com

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=20051228191435.32680.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).