From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: licenses/, profiles/
Date: Sun, 21 Apr 2019 09:17:41 +0000 (UTC) [thread overview]
Message-ID: <1555838238.d0f7c333ba7f881999aeaa629a96e20d39f44889.ulm@gentoo> (raw)
commit: d0f7c333ba7f881999aeaa629a96e20d39f44889
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 21 09:16:26 2019 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Apr 21 09:17:18 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d0f7c333
licenses: Remove unused.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
licenses/keynote | 12 ---
licenses/qpopper | 141 --------------------------------
licenses/yahoo-patent-license-1.2 | 167 --------------------------------------
profiles/license_groups | 4 +-
4 files changed, 2 insertions(+), 322 deletions(-)
diff --git a/licenses/keynote b/licenses/keynote
deleted file mode 100644
index 640f1eb9919..00000000000
--- a/licenses/keynote
+++ /dev/null
@@ -1,12 +0,0 @@
-Copyright (C) 1998, 1999 by Angelos D. Keromytis.
-
-Permission to use, copy, and modify this software without fee
-is hereby granted, provided that this entire notice is included in
-all copies of any software which is or includes a copy or
-modification of this software.
-
-THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR
-IMPLIED WARRANTY. IN PARTICULAR, THE AUTHORS MAKES NO
-REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE
-MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR
-PURPOSE.
diff --git a/licenses/qpopper b/licenses/qpopper
deleted file mode 100644
index bb4cd9e2a94..00000000000
--- a/licenses/qpopper
+++ /dev/null
@@ -1,141 +0,0 @@
-Qpopper(tm) is licensed by QUALCOMM Incorporated under the following
- terms and conditions. ANY USE OF QPOPPER CONSTITUTES AGREEMENT TO
- THESE TERMS.
-
-1. Warranty Disclaimer. QPOPPER SOFTWARE IS PROVIDED TO THE USER "AS
- IS." QUALCOMM MAKES NO WARRANTIES, EITHER EXPRESS OR IMPLIED, WITH
- RESPECT TO THE QPOPPER SOFTWARE AND/OR ASSOCIATED MATERIALS
- PROVIDED TO THE USER, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF
- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR AGAINST
- INFRINGEMENT. QUALCOMM does not warrant that the functions
- contained in the software will meet your requirements, or that the
- operation of the software will be uninterrupted or error-free, or
- that defects in the software will be corrected. Furthermore,
- QUALCOMM does not warrant or make any representations regarding
- the use or the results of the use of the software or any
- documentation provided therewith in terms of their correctness,
- accuracy, reliability, or otherwise. No oral or written
- information or advice given by QUALCOMM or a QUALCOMM
- representative shall create a warranty or in any way increase the
- scope of this warranty.
-
-2. Limitation of Liability. QUALCOMM AND ITS LICENSORS ARE NOT LIABLE
- FOR ANY CLAIMS OR DAMAGES WHATSOEVER ARISING IN CONNECTION WITH
- THE QPOPPER SOFTWARE, INCLUDING WITHOUT LIMITATION PROPERTY
- DAMAGE, PERSONAL INJURY, INTELLECTUAL PROPERTY INFRINGEMENT, LOSS
- OF PROFITS, OR INTERRUPTION OF BUSINESS, OR FOR ANY SPECIAL,
- CONSEQUENTIAL OR INCIDENTAL DAMAGES, HOWEVER CAUSED, WHETHER
- ARISING OUT OF BREACH OF WARRANTY, CONTRACT, TORT (INCLUDING
- NEGLIGENCE), STRICT LIABILITY, OR OTHERWISE.
-
-3. Using and Distributing Qpopper. If a party agrees to these terms
- and conditions, such party may copy and use Qpopper for any
- purpose, and distribute unmodified complete copies of Qpopper to
- any third party provided that such third party must agree to these
- terms and conditions prior to any use of Qpopper. Failure to
- include these license terms when distributing Qpopper shall be a
- material breach of this agreement, and the party committing such
- breach shall defend and indemnify QUALCOMM Incorporated against
- all claims, losses, liabilities, damages, costs and expenses,
- including attorney's fees, which QUALCOMM may incur in connection
- with such breach.
-
-4. Modifying Qpopper. Qpopper consists of (i) intellectual property
- owned by QUALCOMM Incorporated, and (ii) intellectual property
- owned by the Regents of the University of California. Any
- modifications to the U.C.-owned portions of Qpopper are subject to
- the provisions of Section 7 below. A party to this agreement may
- create derivative works of the QUALCOMM-owned portions of the
- Qpopper software, distribute such derivative works to third
- parties, and permit such third parties to copy and use such
- derivative works subject to the following restrictions:
-
- (a) The protocol greeting banner and the CAPA IMPLEMENTATION
- response tag must include clear notification that Qpopper has
- been modified (for example,
- "FooPopper-by-Foo-Networks-hacked-from-Qpopper-4.0").
-
- (b) Detailed notification of all modifications must be clearly and
- conspicuously included within the modified source files, and
- in a separate document. All of the source files and the
- document describing the changes must be distributed with the
- modified software.
-
- (c) When distributing the modified software the distributing party
- must clearly and conspicuously communicate to all recipients
- that the modified software is produced by the party that
- modified the software and is not a QUALCOMM product.
-
- (d) The term "Qpopper" shall not be used in connection with the
- modified software except in a purely factual manner when
- describing the history or development of the software.
-
- (e) The modified software must be licensed to end users using a
- license agreement which expressly states that portions of the
- modified software are based on code owned by QUALCOMM
- Incorporated, that such QUALCOMM code is only provided on the
- terms stated in this agreement, and that QUALCOMM bears no
- responsibility whatsoever for any modifications to the QUALCOMM
- code.
-
- (f) The modifying party shall defend and indemnify QUALCOMM
- Incorporated against all claims, losses, liabilities, damages,
- costs and expenses, including attorney's fees, which QUALCOMM
- may incur in connection with any intellectual property
- infringement or similar claim related to the modified
- software, if such claim is related to that party's
- modifications.
-
-5. Notices. QUALCOMM is a registered trademark and registered service
- mark of QUALCOMM Incorporated. Qpopper is a trademark of QUALCOMM
- Incorporated. QUALCOMM does not grant any party the right to use
- such marks on any modified version of the Qpopper software. All
- other trademarks and service marks are the property of their
- respective owners. The Qpopper software, excluding the portions
- owned by the Regents of the University of California, is Copyright
- 1993-2006 QUALCOMM Incorporated. All rights not expressly granted
- herein are reserved by QUALCOMM.
-
-6. General. This agreement is governed and interpreted in accordance
- with the laws of the State of California without giving effect to
- its conflict of laws provisions. Any claim arising out of or
- related to this agreement must be brought exclusively in the state
- or federal courts located in San Diego County, California. The
- United Nations Convention on Contracts for the International Sale
- of Goods is expressly disclaimed. If any provision of this
- agreement shall be invalid, the validity of the remaining
- provisions of this agreement shall not be affected. This
- agreement is the entire and exclusive agreement between QUALCOMM
- and any user of the Qpopper software with respect to the software
- and supersedes all prior agreements (whether written or oral) and
- other communications related to the software.
-
-7. IMPORTANT.
-
- This software program contains code, and/or derivatives or
- modifications of code originating from the software program
- "Popper." Popper is (c) Copyright 1989-1991 The Regents of the
- University of California, All Rights Reserved. Popper was
- created by Austin Shelton, Information Systems and Technology,
- University of California, Berkeley. Permission from the Regents of
- the University of California to use, copy, modify, and distribute
- the "Popper" software contained herein for any purpose, without
- fee, and without a written agreement is hereby granted, provided
- that the above copyright notice and this paragraph and the
- following two paragraphs appear in all copies. HOWEVER, ADDITIONAL
- PERMISSIONS MAY BE NECESSARY FROM OTHER PERSONS OR ENTITIES, TO
- USE DERIVATIVES OR MODIFICATIONS OF POPPER.
-
- IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY
- PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
- DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THE
- POPPER SOFTWARE, OR ITS DERIVATIVES OR MODIFICATIONS, AND ITS
- DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN
- ADVISED OF THE POSSIBLITY OF SUCH DAMAGE.
-
- THE UNIVERSITY OF CALIFORNIA, SPECIFICALLY DISCLAIMS ANY
- WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
- POPPER SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE
- UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE
- MAINTENANCE, SUPPORT, UPDATES, ENCHANCEMENTS, OR MODIFICATIONS.
diff --git a/licenses/yahoo-patent-license-1.2 b/licenses/yahoo-patent-license-1.2
deleted file mode 100644
index 144257ac93e..00000000000
--- a/licenses/yahoo-patent-license-1.2
+++ /dev/null
@@ -1,167 +0,0 @@
-Yahoo! DomainKeys Patent License Agreement v1.2
-
-Copyright (c) 2006, Yahoo! Inc.
-All rights reserved.
-
-This Yahoo! DomainKeys Patent License Agreement (this "Agreement") is
-between Yahoo! Inc. ("Yahoo!") and you ("Licensee"). By attempting to
-exercise any rights granted under this Agreement, Licensee agrees to be
-bound by all the terms and conditions set forth below, and subject to those
-terms and conditions, Licensee may use the intellectual property described
-below.
-
-1. LICENSE GRANT.
-
-1.1. Subject to the terms and conditions of this Agreement, Licensor hereby
-grants You a royalty-free, perpetual, worldwide, sublicensable,
-non-exclusive license under its rights to the Yahoo! Patent Claims to make,
-use, sell, offer for sale, and/or import Implementations.
-
-2. DEFINITIONS.
-
-2.1. "DomainKeys Developer(s)" means Yahoo, Inc. ("Yahoo!"), Licensor,
-and/or any other individual or entity who distributes Implementations under
-this Agreement.
-
-2.2. "Implementations" means the specific portions of a hardware or
-software implementation expressly required to be compliant with the
-Specifications for the sole purpose of a sender verification solution in
-connection with e-mail.
-
-2.3. "Licensor" means Yahoo! or any other individual or entity that elects
-to use this Agreement to license Yahoo! Patent Claims to any licensee.
-
-2.4. "Specifications" means the specification having submission ID
-"draft-delany-domainkeys-base-01.txt" dated Aug 2004 published through the
-IETF (Internet Engineering Task Force). The Specifications may be found at
-the following link:
-http://antispam.yahoo.com/domainkeys/draft-delany-domainkeys-base-01.txt
-
-2.5. "Yahoo! Patent Claims" shall mean those claims of all Yahoo! foreign
-and domestic patents and patent applications that base their priority on
-U.S. Provisional Patent Application Ser. Nos. 60/497,794, filed Aug. 26,
-2003, or 60/553,300, filed Mar. 15, 2004, or U.S. Patent Application Ser.
-Nos. 10/671,319, filed Sep. 24, 2003, or 10/805,181, filed Mar. 19, 2004.
-
-2.6. "You" or "Your" means an individual, company, or other legal entity
-exercising any rights under this Agreement. Any individual who accepts the
-terms and conditions of this Agreement on behalf of a company or other
-legal entity represents and warrants that the individual has the authority
-to enter into this Agreement on behalf of the company or other legal
-entity.
-
-3. TERMS.
-
-3.1. You agree not to assert against Yahoo!, any other DomainKeys Developer
-or any of their respective licensees under Section 3.4, a patent
-infringement claim based on the manufacture, use, sale, offer for sale
-and/or importation of any Implementations ("Implementation IP Claim").
-
-3.2. To indicate your assent to the terms and conditions of this Agreement
-and in order to obtain a license to make, use, sell, offer for sale, and/or
-import Implementations, You must include, attach or preserve the following
-prominently displayed statement in the source code and object code of any
-such Implementations: "This code incorporates intellectual property owned
-by Yahoo! and licensed pursuant to the Yahoo! DomainKeys Patent License
-Agreement.".
-
-3.3. You will not use the name of Yahoo! to endorse or promote any
-products, services, or Implementations without specific prior written
-permission of Yahoo!. "DomainKeys" is a trademark of Yahoo!. However, You
-may state Your Implementations are "DomainKeys compliant", "supports
-DomainKeys", or is "DomainKeys-enabled", without citation to Yahoo!. You
-must create Your own product or service names or trademarks for Your
-Implementations and You agree not to use the term "DomainKeys" in or as
-part of a name or trademark for Your Implementations.
-
-3.4. You may choose to distribute Implementations under this Agreement or a
-different agreement, provided that:
-
- (a) a copy of this Agreement or the different agreement is included with
- each Implementation along with the following prominently displayed
- statement: "By making, using, selling, offering for sale, importing,
- and/or sublicensing Implementations as permitted, you agree to the terms
- and conditions of the Yahoo! DomainKeys Patent License Agreement or
- other agreement contained herein."; and
-
- (b) if distributed under a different agreement, such different agreement
- contains terms and conditions that (i) provide no fewer rights,
- privileges and immunities to DomainKeys Developers than the terms and
- conditions of this Agreement, including, without limitation, Sections
- 1.1, 3.1, 3.4, 3.7, 4.1, 4.2, and 4.3.
-
-3.5. You acknowledge that implementations of the Specifications may be
-subject to U.S. export restriction and other applicable national and
-international laws. You agree to comply with all export, re-export, or
-import restrictions, laws, or regulations.
-
-3.6. Yahoo!, and only Yahoo!, may, from time to time and at its sole
-discretion, update or modify the terms of this Agreement. If Yahoo! makes
-any such modifications, You may continue under the terms and conditions of
-this Agreement or agree to the updated or modified terms and conditions.
-For the most recent version of this Agreement please contact Yahoo!.
-
-3.7. This Agreement and the rights hereunder will terminate:
-
- (a) automatically without notice from Yahoo!, if You at any time during
- the term of this Agreement assert any Implementation IP Claim against
- Yahoo!;
-
- (b) upon written notice from Yahoo!, if You at any time during the term
- of this Agreement assert any Implementation IP Claim against any
- DomainKeys Developer (other than Yahoo!) or any licensees of any
- DomainKeys Developer; or
-
- (c) where (a) or (b) do not apply, automatically without notice from
- Yahoo!, if You fail to comply with any term(s) of this Agreement and
- fail to cure such breach within 30 days of You becoming aware of such
- breach.
-
-3.8. This Agreement constitutes the entire agreement between the parties
-with respect to the subject matter hereof. This Agreement shall be governed
-by and construed under the laws of the United States and the State of
-California without giving effect to California conflict of law provisions
-or to construction provisions favoring either party. All actions arising
-out of or relating to this Agreement that involve Yahoo! as a party will be
-adjudicated exclusively by the Superior Court of the State of California
-for the County of Santa Clara or the United States District Court for the
-Northern District of California.
-
-3.9. In the event that any provision of this Agreement is deemed to be
-invalid, such invalidity shall not affect the remainder of this Agreement.
-
-4. LEGAL DISCLAIMERS.
-
-4.1. THE YAHOO! PATENT CLAIMS, THIS AGREEMENT, THE DOMAINKEYS TRADEMARK,
-AND THE SPECIFICATIONS ARE PROVIDED ON AN "AS IS" BASIS, WITHOUT
-REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
-IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY REPRESENTATIONS, WARRANTIES OR
-CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A
-PARTICULAR PURPOSE. You are solely responsible for determining the
-appropriateness of exercising any rights under this Agreement and using the
-Specifications and the DomainKeys trademark and assume all risks associated
-in connection therewith, including, but not limited to, the risks and costs
-of program errors, compliance with applicable laws, damage to or loss of
-data, programs or equipment, and unavailability or interruption of
-operations.
-
-4.2. You expressly acknowledge and agree that no assurances are provided by
-DomainKeys Developers with respect to the validity of the Yahoo! Patent
-Claims or that the Specifications, the DomainKeys trademark or any
-implementations related to the Specifications or the DomainKeys trademark
-do not infringe or misappropriate the patent, trademark or other
-intellectual property rights of any other entity. DomainKeys Developers
-disclaim any liability to You for claims brought by any other person or
-entity based on infringement or misappropriation of intellectual property
-rights or otherwise. As a condition to exercising the rights and licenses
-granted hereunder, You hereby assume sole responsibility to secure any
-other intellectual property rights needed.
-
-4.3. DOMAINKEYS DEVELOPERS SHALL NOT HAVE ANY LIABILITY FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY
-THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE EXERCISE
-OF ANY RIGHTS UNDER THIS AGREEMENT, EVEN IF ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES, AND EVEN IF THE REMEDIES PROVIDED FOR IN THIS AGREEMENT FAIL
-OF THEIR ESSENTIAL PURPOSE.
diff --git a/profiles/license_groups b/profiles/license_groups
index 52fbcec2d6a..c4f9e073901 100644
--- a/profiles/license_groups
+++ b/profiles/license_groups
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
# Please report bugs or other requests at bugs.gentoo.org and assign to
@@ -30,7 +30,7 @@ OSI-APPROVED AFL-3.0 AGPL-3 AGPL-3+ Apache-1.1 Apache-2.0 APL-1.0 APSL-2 Artisti
# Licenses in this list should NOT appear directly or indirectly in
# @FSF-APPROVED or @OSI-APPROVED.
# Note: Licenses for fonts should be included in @MISC-FREE-DOCS.
-MISC-FREE ACE Allegro alternate AMPAS bea.ri.jsr173 BEER-WARE boehm-gc BSD-1 BSD-with-attribution buddy bufexplorer.vim BZIP2 canfep CAOSL CDDL-Schily CeCILL-C CMake CPL-0.5 CRACKLIB Crypt-IDEA DES docbook dom4j eGenixPublic-1.1 ElementTree Emacs ErlPL-1.1 FastCGI feh File-MMagic Flashpix FLEX flexmock FLTK freetts FVWM gd gsm HTML-Tidy htmlc iASL icu IDPL imagemagick Info-ZIP inner-net ipadic ipx-utils Ispell JasPer2.0 JDOM JNIC JOVE keynote LambdaMOO LIBGLOSS libmng libpng libpng2 libtiff LLVM-Grant LPPL-1.3 LPPL-1.3b lsof Mail-Sendmail mapm-4.9.5 matplotlib Mini-XML minpack MIT-with-advertising mm mpich2 NCSA-HDF netcat NEWLIB ngrep Old-MIT openafs-krb5-a Openwall otter PCRE perforce photopc PHP-2.02 pngcrush pngnq Princeton psutils qmail-nelson rc rdisc regexp-UofT repoze RSA rwpng scanlogd Sendmail Sendmail-Open-Source shrimp SMAIL Snd SNIA SSLeay Subversion SVFL symlinks tablelist tcltk tcp_wrappers_license telegram TeX TeX-other-free the-Click-license Time-Format Time-modules
tm-align torque-2.5 totd Toyoda UCAR-Unidata URT VTK w3m wxWinLL-3.1 x2x xbatt xboing XC Xdebug xtrs xvt YaTeX yuuji ZSH
+MISC-FREE ACE Allegro alternate AMPAS bea.ri.jsr173 BEER-WARE boehm-gc BSD-1 BSD-with-attribution buddy bufexplorer.vim BZIP2 canfep CAOSL CDDL-Schily CeCILL-C CMake CPL-0.5 CRACKLIB Crypt-IDEA DES docbook dom4j eGenixPublic-1.1 ElementTree Emacs ErlPL-1.1 FastCGI feh File-MMagic Flashpix FLEX flexmock FLTK freetts FVWM gd gsm HTML-Tidy htmlc iASL icu IDPL imagemagick Info-ZIP inner-net ipadic ipx-utils Ispell JasPer2.0 JDOM JNIC JOVE LambdaMOO LIBGLOSS libmng libpng libpng2 libtiff LLVM-Grant LPPL-1.3 LPPL-1.3b lsof Mail-Sendmail mapm-4.9.5 matplotlib Mini-XML minpack MIT-with-advertising mm mpich2 NCSA-HDF netcat NEWLIB ngrep Old-MIT openafs-krb5-a Openwall otter PCRE perforce photopc PHP-2.02 pngcrush pngnq Princeton psutils qmail-nelson rc rdisc regexp-UofT repoze RSA rwpng scanlogd Sendmail Sendmail-Open-Source shrimp SMAIL Snd SNIA SSLeay Subversion SVFL symlinks tablelist tcltk tcp_wrappers_license telegram TeX TeX-other-free the-Click-license Time-Format Time-modules tm-alig
n torque-2.5 totd Toyoda UCAR-Unidata URT VTK w3m wxWinLL-3.1 x2x xbatt xboing XC Xdebug xtrs xvt YaTeX yuuji ZSH
# Metaset for all free software
FREE-SOFTWARE @FSF-APPROVED @OSI-APPROVED @MISC-FREE
next reply other threads:[~2019-04-21 9:17 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 9:17 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-05 11:34 [gentoo-commits] repo/gentoo:master commit in: licenses/, profiles/ Andrew Ammerlaan
2024-06-11 16:41 Ulrich Müller
2024-05-01 14:14 Michał Górny
2023-04-12 13:09 David Seifert
2023-01-21 16:40 Ulrich Müller
2023-01-12 11:48 Ulrich Müller
2022-08-31 9:58 Ionen Wolkens
2022-06-22 8:41 Michał Górny
2022-04-05 19:50 Ulrich Müller
2022-02-12 16:50 Michał Górny
2021-09-08 6:29 Robin H. Johnson
2021-06-27 7:26 Ulrich Müller
2021-05-13 16:12 Ulrich Müller
2021-05-09 4:42 Sam James
2021-01-08 17:34 Ulrich Müller
2020-11-15 9:35 Michał Górny
2020-10-25 17:39 Andreas K. Hüttel
2020-10-10 6:07 Michał Górny
2020-09-25 14:32 Michał Górny
2020-06-09 17:21 Ulrich Müller
2020-03-25 11:17 Joonas Niilola
2020-03-21 10:57 Ulrich Müller
2020-02-11 7:39 Ulrich Müller
2020-01-18 11:50 Ulrich Müller
2019-12-28 10:18 Ulrich Müller
2019-12-11 19:18 Ulrich Müller
2019-12-01 21:23 Ulrich Müller
2019-11-03 9:29 Michał Górny
2019-09-15 14:58 Michał Górny
2019-07-05 10:43 Ulrich Müller
2019-05-16 6:37 Ulrich Müller
2019-04-24 21:20 Ulrich Müller
2018-09-13 19:23 Ulrich Müller
2018-08-17 20:04 Ulrich Müller
2018-03-05 19:21 Ulrich Müller
2018-02-06 13:52 Eray Aslan
2017-11-23 22:14 Ulrich Müller
2017-09-14 17:09 Ulrich Müller
2017-08-19 6:56 Ulrich Müller
2017-06-07 10:50 Tony Vroon
2017-06-06 6:52 Ulrich Müller
2017-04-20 9:06 Ulrich Müller
2017-04-20 9:06 Ulrich Müller
2017-03-18 9:09 Michael Palimaka
2017-01-14 18:14 Michał Górny
2016-10-25 22:48 Ulrich Müller
2016-10-18 16:59 Ulrich Müller
2016-08-03 20:59 Austin English
2016-06-26 22:40 Ulrich Müller
2016-06-09 0:40 Ulrich Müller
2016-05-01 20:06 Ulrich Müller
2016-05-01 17:33 Ulrich Müller
2016-03-19 11:19 Ian Delaney
2016-01-19 8:37 Patrice Clement
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=1555838238.d0f7c333ba7f881999aeaa629a96e20d39f44889.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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