Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Current Groff is really GPLv3!
Date: Fri,  9 Aug 2013 13:46:38 -0700	[thread overview]
Message-ID: <1376081200-12061-1-git-send-email-sgw@linux.intel.com> (raw)

Turns out that a groff update was done sometime ago, and while committer
noted the license checksum changed, they did not verify the true nature
of the change.  I caught this by total chance looking at the license 
manifest directory.

Saul Wold (2):
  groff: Add GPLv2 version
  groff: Fix License to be GPLv3

 .../groff-1.18.1.4/groff-1.18.1.4-remove-mom.patch | 35 ++++++++++++++++
 .../groff/groff-1.18.1.4/man-local.patch           | 32 +++++++++++++++
 .../groff/groff-1.18.1.4/mdoc-local.patch          | 31 +++++++++++++++
 meta/recipes-extended/groff/groff_1.18.1.4.bb      | 46 ++++++++++++++++++++++
 meta/recipes-extended/groff/groff_1.22.2.bb        |  2 +-
 5 files changed, 145 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-extended/groff/groff-1.18.1.4/groff-1.18.1.4-remove-mom.patch
 create mode 100644 meta/recipes-extended/groff/groff-1.18.1.4/man-local.patch
 create mode 100644 meta/recipes-extended/groff/groff-1.18.1.4/mdoc-local.patch
 create mode 100644 meta/recipes-extended/groff/groff_1.18.1.4.bb

-- 
1.8.1.4



             reply	other threads:[~2013-08-09 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 20:46 Saul Wold [this message]
2013-08-09 20:46 ` [PATCH 1/2] groff: Add GPLv2 version Saul Wold
2013-08-09 20:46 ` [PATCH 2/2] groff: Fix License to be GPLv3 Saul Wold

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=1376081200-12061-1-git-send-email-sgw@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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