public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d-mob06 at gmx dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug manual/13792] New: Which license applies to the code examples in the manual?
Date: Thu, 01 Mar 2012 11:17:00 -0000	[thread overview]
Message-ID: <bug-13792-131@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13792
           Summary: Which license applies to the code examples in the
                    manual?
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: manual
        AssignedTo: unassigned@sourceware.org
        ReportedBy: d-mob06@gmx.de
                CC: roland@gnu.org
    Classification: Unclassified


What is the license for the code examples listed in the manual?

I want to use the rather simple example of subtracting a struct timeval in my
project. You can find it here:
www.gnu.org/software/libc/manual/html_node/Elapsed-Time.html

What license does apply? The manual itself is under the GNU Free Documentation
License. What's the deal with the code examples? The closest in the GNU FDL is
the following paragraph at the end:

"If your document contains nontrivial examples of program code, we recommend
releasing these examples in parallel under your choice of free software
license, such as the GNU General Public License, to permit their use in free
software."

A clarification would be very much appreciated.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-03-01 11:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 11:17 d-mob06 at gmx dot de [this message]
2012-03-02 23:53 ` [Bug manual/13792] " roland at gnu dot org
2012-03-03  0:54 ` roland at gnu dot org
2012-03-03  1:39 ` jsm28 at gcc dot gnu.org
2012-03-07  9:23 ` david.martin.mailbox at googlemail dot com
2012-03-07  9:26 ` david.martin.mailbox at googlemail dot com
2014-06-26 14:03 ` fweimer at redhat 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=bug-13792-131@http.sourceware.org/bugzilla/ \
    --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).