public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "BM-2cVqnDuYbAU5do2DfJTrN7ZbAJ246S4Xix at bitmessage dot ch" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16901] Two files have non-free licenses (modification is not explicitly allowed)
Date: Sun, 04 May 2014 08:13:00 -0000	[thread overview]
Message-ID: <bug-16901-4717-CBNhCsQFUw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16901-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16901

--- Comment #1 from Riley Baird <BM-2cVqnDuYbAU5do2DfJTrN7ZbAJ246S4Xix at bitmessage dot ch> ---
Also, just noticed: /libiberty/strcasecmp.c and /libiberty/strncasecmp.c also
don't allow modification. License text:

/*
 * Copyright (c) 1987 Regents of the University of California.
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms are permitted
 * provided that this notice is preserved and that due credit is given
 * to the University of California at Berkeley. The name of the University
 * may not be used to endorse or promote products derived from this
 * software without specific written prior permission. This software
 * is provided ``as is'' without express or implied warranty.
 */

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2014-05-04  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04  8:02 [Bug gdb/16901] New: " BM-2cVqnDuYbAU5do2DfJTrN7ZbAJ246S4Xix at bitmessage dot ch
2014-05-04  8:13 ` BM-2cVqnDuYbAU5do2DfJTrN7ZbAJ246S4Xix at bitmessage dot ch [this message]
2014-05-04 11:55 ` [Bug gdb/16901] " BM-2cVqnDuYbAU5do2DfJTrN7ZbAJ246S4Xix at bitmessage dot ch

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-16901-4717-CBNhCsQFUw@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).