public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/26306] Confusion in malloc.c about the fastbins size check.
Date: Fri, 31 Jul 2020 10:01:11 +0000 [thread overview]
Message-ID: <bug-26306-131-rWFptoy2i4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26306-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26306
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to hk from comment #3)
> Is it okay if i propose a patch for this .
How large is the patch going to be? If it changes just a few lines (fewer than
15), we don't need copyright assignment according to guidance we have received
from the Free Software Foundation.
For larger changes, you will have to file paperwork with the Free Software
Foundation:
https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_Assignment
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-07-31 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 7:19 [Bug malloc/26306] New: " hkrawbytes at gmail dot com
2020-07-28 9:53 ` [Bug malloc/26306] " fweimer at redhat dot com
2020-07-28 10:07 ` hkrawbytes at gmail dot com
2020-07-28 10:08 ` hkrawbytes at gmail dot com
2020-07-31 10:01 ` fweimer at redhat dot com [this message]
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=bug-26306-131-rWFptoy2i4@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).