From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: licenses/
Date: Fri, 20 Oct 2023 17:04:48 +0000 (UTC) [thread overview]
Message-ID: <1697821478.1570d79b8f41b7c28764866b68e86c78df48f2a8.ulm@gentoo> (raw)
commit: 1570d79b8f41b7c28764866b68e86c78df48f2a8
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 20 16:28:49 2023 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Oct 20 17:04:38 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1570d79b
licenses: Delete trailing whitespace in LPPL-*
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
licenses/LPPL-1.2 | 34 +++++++++++++++-------------------
licenses/LPPL-1.3 | 41 ++++++++++++++++++++---------------------
licenses/LPPL-1.3c | 49 ++++++++++++++++++++++++-------------------------
3 files changed, 59 insertions(+), 65 deletions(-)
diff --git a/licenses/LPPL-1.2 b/licenses/LPPL-1.2
index 5b05fe86893c..6822ceef827d 100644
--- a/licenses/LPPL-1.2
+++ b/licenses/LPPL-1.2
@@ -1,4 +1,3 @@
-
The LaTeX Project Public License
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
@@ -44,7 +43,7 @@ We, the LaTeX3 Project, believe that the conditions below give you
the freedom to make and distribute modified versions of The Program
that conform with whatever technical specifications you wish while
maintaining the availability, integrity, and reliability of
-The Program. If you do not see how to achieve your goal while
+The Program. If you do not see how to achieve your goal while
meeting these conditions, then read the document `cfgguide.tex'
in the base LaTeX distribution for suggestions.
@@ -65,32 +64,32 @@ following eight conditions are met:
distribution of a modified version of the file as described below
in the subsection `Additional Conditions on Individual Files of
The Program'.
-
+
2. If the file is a LaTeX software file, then you must meet any
applicable additional conditions on the distribution of a modified
version of the file that are described below in the subsection
`Additional Conditions on LaTeX Software Files'.
-
+
3. You must not distribute the modified file with the filename of the
original file.
-
+
4. In the modified file, you must acknowledge the authorship and
name of the original file, and the name (if any) of the program
which contains it.
-
+
5. You must change any identification string in the file to indicate
clearly that the modified file is not part of The Program.
-
+
6. You must change any addresses in the modified file for the
reporting of errors in the file or in The Program generally to
ensure that reports for files no longer maintained by the original
maintainers will be directed to the maintainers of the modified
files.
-
+
7. You must distribute the modified file under a license that forbids
distribution both of the modified file and of any files derived
from the modified file with the filename of the original file.
-
+
8. You must do either (A) or (B):
(A) distribute a copy of The Program (that is, a complete,
@@ -105,7 +104,7 @@ following eight conditions are met:
(B) provide to those who receive the modified file information
that is sufficient for them to obtain a copy of The Program;
for example, you may provide a Uniform Resource Locator (URL)
- for a site that you expect will provide them with a copy of
+ for a site that you expect will provide them with a copy of
The Program free of charge (either the version from which
your modification is derived, or perhaps a later version).
@@ -131,7 +130,7 @@ The conditions above are not intended to prohibit, and hence do not
apply to, the updating, by any method, of a file so that it becomes
identical to the latest version of that file of The Program.
-
+
A Recommendation on Modification Without Distribution
-----------------------------------------------------
@@ -173,7 +172,7 @@ above, apply to the file according to its filename extension:
- You may not modify any file with filename extension `.ins' since
these are installation files containing the legal notices that are
placed in the files they generate.
-
+
- You may distribute modified versions of files with filename
extension `.fd' (LaTeX font definition files) under the standard
conditions of the LPPL as described above. You may also distribute
@@ -189,7 +188,7 @@ above, apply to the file according to its filename extension:
extension `.cfg' (configuration files) with their original names.
The Program may (and usually will) specify the range of commands
that are allowed in a particular configuration file.
-
+
Because of portability and exchangeability issues in LaTeX software,
The LaTeX3 Project deprecates the distribution of modified versions of
components of LaTeX or of generally available contributed code for them,
@@ -266,7 +265,7 @@ Here is an example of such a notice and statement:
% of this license or (at your option) any later version.
% The latest version of this license is in
% http://www.latex-project.org/lppl.txt
- % and version 1.2 or later is part of all distributions of LaTeX
+ % and version 1.2 or later is part of all distributions of LaTeX
% version 1999/12/01 or later.
%
% This program consists of the files pig.dtx and pig.ins
@@ -296,7 +295,7 @@ Important Recommendations
to comprise The Program.
Noting Exceptional Files
-
+
If The Program contains any files bearing additional conditions on
modification, or on distribution of modified versions, of those
files (other than those listed in `Additional Conditions on LaTeX
@@ -310,9 +309,6 @@ Important Recommendations
modification. LaTeX configuration files (with filename extension
`.cfg') are examples of files bearing less restrictive conditions
on the distribution of a modified version of the file. The
- additional conditions on LaTeX software given above are examples
+ additional conditions on LaTeX software given above are examples
of declaring a category of files bearing exceptional additional
conditions.
-
-
-
diff --git a/licenses/LPPL-1.3 b/licenses/LPPL-1.3
index 81db0b038c93..737f77b3710f 100644
--- a/licenses/LPPL-1.3
+++ b/licenses/LPPL-1.3
@@ -1,4 +1,3 @@
-
The LaTeX Project Public License
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
@@ -45,11 +44,11 @@ In this license document the following terms are used:
`Work'
Any work being distributed under this License.
-
+
`Derived Work'
Any work that under any applicable law is derived from the Work.
- `Modification'
+ `Modification'
Any procedure that produces a Derived Work under any applicable
law -- for example, the production of a file containing an
original file associated with the Work or a significant portion of
@@ -59,7 +58,7 @@ In this license document the following terms are used:
`Modify'
To apply any procedure that produces a Derived Work under any
applicable law.
-
+
`Distribution'
Making copies of the Work available from one person to another, in
whole or in part. Distribution includes (but is not limited to)
@@ -80,9 +79,9 @@ In this license document the following terms are used:
no such explicit nomination then it is the `Copyright Holder' under
any applicable law.
- `Base Interpreter'
+ `Base Interpreter'
A program or process that is normally needed for running or
- interpreting a part or the whole of the Work.
+ interpreting a part or the whole of the Work.
A Base Interpreter may depend on external components but these
are not considered part of the Base Interpreter provided that each
external component clearly identifies itself whenever it is used
@@ -128,8 +127,8 @@ the Derived Work.
distribute a Derived Work provided the following conditions are met
for every component of the Work unless that component clearly states
in the copyright notice that it is exempt from that condition. Only
-the Current Maintainer is allowed to add such statements of exemption
-to a component of the Work.
+the Current Maintainer is allowed to add such statements of exemption
+to a component of the Work.
a. If a component of this Derived Work can be a direct replacement
for a component of the Work when that component is used with the
@@ -139,13 +138,13 @@ to a component of the Work.
clearly and unambiguously identifies itself as a modified version
of this component to the user when used interactively with that
Base Interpreter.
-
+
b. Every component of the Derived Work contains prominent notices
detailing the nature of the changes to that component, or a
prominent reference to another file that is distributed as part
of the Derived Work and that contains a complete and accurate log
of the changes.
-
+
c. No information in the Derived Work implies that any persons,
including (but not limited to) the authors of the original version
of the Work, provide any support, including (but not limited to)
@@ -155,7 +154,7 @@ to a component of the Work.
d. You distribute at least one of the following with the Derived Work:
- 1. A complete, unmodified copy of the Work;
+ 1. A complete, unmodified copy of the Work;
if your distribution of a modified component is made by
offering access to copy the modified component from a
designated place, then offering equivalent access to copy
@@ -182,15 +181,15 @@ format, where the Work or that Derived Work (in whole or in part) is
then produced by applying some process to that format, does not relax or
nullify any sections of this license as they pertain to the results of
applying that process.
-
+
10. a. A Derived Work may be distributed under a different license
provided that license itself honors the conditions listed in
Clause 6 above, in regard to the Work, though it does not have
to honor the rest of the conditions in this license.
-
+
b. If a Derived Work is distributed under this license, that
Derived Work must provide sufficient documentation as part of
- itself to allow each recipient of that Derived Work to honor the
+ itself to allow each recipient of that Derived Work to honor the
restrictions in Clause 6 above, concerning changes from the Work.
11. This license places no restrictions on works that are unrelated to
@@ -259,7 +258,7 @@ the Work through the following steps:
a. If it is being maintained, then ask the Current Maintainer
to update their communication data within one month.
-
+
b. If the search is unsuccessful or no action to resume active
maintenance is taken by the Current Maintainer, then announce
within the pertinent community your intention to take over
@@ -269,17 +268,17 @@ the Work through the following steps:
3a. If the Current Maintainer is reachable and agrees to pass
maintenance of the Work to you, then this takes effect
immediately upon announcement.
-
+
b. If the Current Maintainer is not reachable and the Copyright
Holder agrees that maintenance of the Work be passed to you,
- then this takes effect immediately upon announcement.
-
+ then this takes effect immediately upon announcement.
+
4. If you make an `intention announcement' as described in 2b. above
and after three months your intention is challenged neither by
the Current Maintainer nor by the Copyright Holder nor by other
people, then you may arrange for the Work to be changed so as
to name you as the (new) Current Maintainer.
-
+
5. If the previously unreachable Current Maintainer becomes
reachable once more within three months of a change completed
under the terms of 3b) or 4), then that Current Maintainer must
@@ -362,7 +361,7 @@ Here is an example of such a notice and statement:
% version 2003/12/01 or later.
%
% This work has the LPPL maintenance status "maintained".
- %
+ %
% This Current Maintainer of this work is M. Y. Name.
%
% This work consists of the files pig.dtx and pig.ins
@@ -393,7 +392,7 @@ Important Recommendations
using a line such as:
% This work consists of all files listed in manifest.txt.
-
+
in that place. In the absence of an unequivocal list it might be
impossible for the licensee to determine what is considered by you
to comprise the Work and, in such a case, the licensee would be
diff --git a/licenses/LPPL-1.3c b/licenses/LPPL-1.3c
index 90e5e3ab7974..b0f86d50d447 100644
--- a/licenses/LPPL-1.3c
+++ b/licenses/LPPL-1.3c
@@ -16,8 +16,8 @@ which the the LaTeX kernel and the base LaTeX packages are distributed.
You may use this license for any work of which you hold the copyright
and which you wish to distribute. This license may be particularly
-suitable if your work is TeX-related (such as a LaTeX package), but
-it is written in such a way that you can use it even if your work is
+suitable if your work is TeX-related (such as a LaTeX package), but
+it is written in such a way that you can use it even if your work is
unrelated to TeX.
The section `WHETHER AND HOW TO DISTRIBUTE WORKS UNDER THIS LICENSE',
@@ -44,11 +44,11 @@ In this license document the following terms are used:
`Work'
Any work being distributed under this License.
-
+
`Derived Work'
Any work that under any applicable law is derived from the Work.
- `Modification'
+ `Modification'
Any procedure that produces a Derived Work under any applicable
law -- for example, the production of a file containing an
original file associated with the Work or a significant portion of
@@ -58,7 +58,7 @@ In this license document the following terms are used:
`Modify'
To apply any procedure that produces a Derived Work under any
applicable law.
-
+
`Distribution'
Making copies of the Work available from one person to another, in
whole or in part. Distribution includes (but is not limited to)
@@ -79,16 +79,16 @@ In this license document the following terms are used:
no such explicit nomination then it is the `Copyright Holder' under
any applicable law.
- `Base Interpreter'
+ `Base Interpreter'
A program or process that is normally needed for running or
- interpreting a part or the whole of the Work.
+ interpreting a part or the whole of the Work.
A Base Interpreter may depend on external components but these
are not considered part of the Base Interpreter provided that each
external component clearly identifies itself whenever it is used
interactively. Unless explicitly specified when applying the
license to the Work, the only applicable Base Interpreter is a
- `LaTeX-Format' or in the case of files belonging to the
+ `LaTeX-Format' or in the case of files belonging to the
`LaTeX-format' a program implementing the `TeX language'.
@@ -129,8 +129,8 @@ the Derived Work.
distribute a Derived Work provided the following conditions are met
for every component of the Work unless that component clearly states
in the copyright notice that it is exempt from that condition. Only
-the Current Maintainer is allowed to add such statements of exemption
-to a component of the Work.
+the Current Maintainer is allowed to add such statements of exemption
+to a component of the Work.
a. If a component of this Derived Work can be a direct replacement
for a component of the Work when that component is used with the
@@ -140,13 +140,13 @@ to a component of the Work.
clearly and unambiguously identifies itself as a modified version
of this component to the user when used interactively with that
Base Interpreter.
-
+
b. Every component of the Derived Work contains prominent notices
detailing the nature of the changes to that component, or a
prominent reference to another file that is distributed as part
of the Derived Work and that contains a complete and accurate log
of the changes.
-
+
c. No information in the Derived Work implies that any persons,
including (but not limited to) the authors of the original version
of the Work, provide any support, including (but not limited to)
@@ -156,7 +156,7 @@ to a component of the Work.
d. You distribute at least one of the following with the Derived Work:
- 1. A complete, unmodified copy of the Work;
+ 1. A complete, unmodified copy of the Work;
if your distribution of a modified component is made by
offering access to copy the modified component from a
designated place, then offering equivalent access to copy
@@ -183,15 +183,15 @@ format, where the Work or that Derived Work (in whole or in part) is
then produced by applying some process to that format, does not relax or
nullify any sections of this license as they pertain to the results of
applying that process.
-
+
10. a. A Derived Work may be distributed under a different license
provided that license itself honors the conditions listed in
Clause 6 above, in regard to the Work, though it does not have
to honor the rest of the conditions in this license.
-
+
b. If a Derived Work is distributed under a different license, that
Derived Work must provide sufficient documentation as part of
- itself to allow each recipient of that Derived Work to honor the
+ itself to allow each recipient of that Derived Work to honor the
restrictions in Clause 6 above, concerning changes from the Work.
11. This license places no restrictions on works that are unrelated to
@@ -260,7 +260,7 @@ the Work through the following steps:
a. If it is being maintained, then ask the Current Maintainer
to update their communication data within one month.
-
+
b. If the search is unsuccessful or no action to resume active
maintenance is taken by the Current Maintainer, then announce
within the pertinent community your intention to take over
@@ -270,17 +270,17 @@ the Work through the following steps:
3a. If the Current Maintainer is reachable and agrees to pass
maintenance of the Work to you, then this takes effect
immediately upon announcement.
-
+
b. If the Current Maintainer is not reachable and the Copyright
Holder agrees that maintenance of the Work be passed to you,
- then this takes effect immediately upon announcement.
-
+ then this takes effect immediately upon announcement.
+
4. If you make an `intention announcement' as described in 2b. above
and after three months your intention is challenged neither by
the Current Maintainer nor by the Copyright Holder nor by other
people, then you may arrange for the Work to be changed so as
to name you as the (new) Current Maintainer.
-
+
5. If the previously unreachable Current Maintainer becomes
reachable once more within three months of a change completed
under the terms of 3b) or 4), then that Current Maintainer must
@@ -363,7 +363,7 @@ Here is an example of such a notice and statement:
% version 2005/12/01 or later.
%
% This work has the LPPL maintenance status `maintained'.
- %
+ %
% The Current Maintainer of this work is M. Y. Name.
%
% This work consists of the files pig.dtx and pig.ins
@@ -377,7 +377,7 @@ referring to any `LaTeX-Format', and both `Copyright Holder' and
`Current Maintainer' referring to the person `M. Y. Name'.
If you do not want the Maintenance section of LPPL to apply to your
-Work, change `maintained' above into `author-maintained'.
+Work, change `maintained' above into `author-maintained'.
However, we recommend that you use `maintained', as the Maintenance
section was added in order to ensure that your Work remains useful to
the community even when you can no longer maintain and support it
@@ -407,10 +407,9 @@ Important Recommendations
using a line such as:
% This work consists of all files listed in manifest.txt.
-
+
in that place. In the absence of an unequivocal list it might be
impossible for the licensee to determine what is considered by you
to comprise the Work and, in such a case, the licensee would be
entitled to make reasonable conjectures as to which files comprise
the Work.
-
next reply other threads:[~2023-10-20 17:04 UTC|newest]
Thread overview: 279+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 17:04 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-24 2:02 [gentoo-commits] repo/gentoo:master commit in: licenses/ Sam James
2025-02-19 22:21 Sam James
2025-01-20 13:52 Ulrich Müller
2025-01-19 20:50 Ulrich Müller
2025-01-19 20:50 Ulrich Müller
2024-12-17 19:52 Ionen Wolkens
2024-10-14 7:21 Andrew Ammerlaan
2024-09-29 12:42 Conrad Kostecki
2024-09-12 10:42 Ulrich Müller
2024-09-05 12:55 Michael Orlitzky
2024-08-20 9:39 Ulrich Müller
2024-07-27 12:44 Ulrich Müller
2024-07-26 15:02 Viorel Munteanu
2024-06-29 14:42 Ulrich Müller
2024-06-24 15:47 James Le Cuirot
2024-06-08 14:11 Michał Górny
2024-05-16 5:28 Ulrich Müller
2024-01-15 19:59 Ulrich Müller
2024-01-15 16:30 Ulrich Müller
2024-01-15 9:17 Ulrich Müller
2024-01-06 8:33 Viorel Munteanu
2024-01-01 17:54 Viorel Munteanu
2023-12-17 12:03 Michał Górny
2023-12-01 13:21 Ulrich Müller
2023-11-25 9:45 James Le Cuirot
2023-10-24 13:18 Miroslav Šulc
2023-09-23 14:06 Conrad Kostecki
2023-09-20 21:11 Andreas K. Hüttel
2023-08-21 19:02 Ulrich Müller
2023-08-18 8:21 Sam James
2023-08-12 9:44 Ulrich Müller
2023-07-27 16:36 Ulrich Müller
2023-07-15 8:14 Ulrich Müller
2023-03-30 8:31 Marek Szuba
2023-03-30 8:31 Marek Szuba
2023-03-27 10:24 Miroslav Šulc
2023-02-28 13:12 Marek Szuba
2023-02-01 17:13 Ulrich Müller
2023-01-27 20:48 Ulrich Müller
2023-01-21 16:54 Ulrich Müller
2023-01-12 12:29 Ulrich Müller
2023-01-10 8:34 Sam James
2023-01-07 9:05 Ulrich Müller
2022-11-22 17:58 Ulrich Müller
2022-11-22 17:54 Ulrich Müller
2022-11-21 8:14 Sam James
2022-11-17 17:42 Ulrich Müller
2022-10-02 22:00 Andreas K. Hüttel
2022-08-30 21:09 Patrick McLean
2022-08-29 22:53 Sam James
2022-08-26 12:13 Ulrich Müller
2022-08-26 12:13 Ulrich Müller
2022-07-02 19:30 William Hubbs
2022-06-13 14:46 Ulrich Müller
2022-05-10 12:32 Mike Pagano
2022-04-23 8:47 Ulrich Müller
2022-04-23 8:01 Hans de Graaff
2022-04-10 14:53 James Le Cuirot
2022-04-07 21:28 Ulrich Müller
2022-03-31 22:36 Patrick McLean
2022-03-31 21:50 Patrick McLean
2022-03-19 12:37 Conrad Kostecki
2022-02-13 17:05 Andrew Ammerlaan
2022-02-13 16:27 Ulrich Müller
2022-02-06 14:52 James Le Cuirot
2022-02-04 23:25 Conrad Kostecki
2021-09-21 10:49 Ulrich Müller
2021-09-21 10:49 Ulrich Müller
2021-09-21 10:06 Ulrich Müller
2021-09-21 7:54 Michał Górny
2021-09-02 10:29 Ulrich Müller
2021-08-16 22:55 Davide Pesavento
2021-07-23 5:45 Miroslav Šulc
2021-07-06 22:09 William Hubbs
2021-06-30 22:08 William Hubbs
2021-05-27 9:07 Ulrich Müller
2021-05-27 7:26 Joonas Niilola
2021-05-27 7:26 Joonas Niilola
2021-05-23 17:11 Ulrich Müller
2021-05-19 21:07 Ulrich Müller
2021-05-12 10:00 Ulrich Müller
2021-05-07 8:27 Ulrich Müller
2021-04-22 15:28 Sam James
2021-04-22 15:28 Sam James
2021-03-30 7:25 Joonas Niilola
2021-02-09 9:29 罗百科
2021-01-27 5:55 Sam James
2021-01-08 15:24 Ben Kohler
2020-12-18 15:53 Stephan Hartmann
2020-12-02 12:09 Alexey Shvetsov
2020-11-26 5:06 Sam James
2020-10-28 7:25 Stephan Hartmann
2020-10-26 8:21 Michał Górny
2020-10-15 9:53 Jeroen Roovers
2020-10-07 8:10 Michał Górny
2020-10-04 6:58 Jeroen Roovers
2020-10-01 20:44 William Hubbs
2020-10-01 20:24 William Hubbs
2020-09-28 8:39 Michael Haubenwallner
2020-09-16 8:37 Marek Szuba
2020-09-16 8:04 Joonas Niilola
2020-08-27 15:07 Conrad Kostecki
2020-08-07 6:00 Michał Górny
2020-08-03 12:46 Marek Szuba
2020-07-29 13:57 Marek Szuba
2020-07-29 13:57 Marek Szuba
2020-07-21 10:56 Mark Wright
2020-06-24 21:04 Ulrich Müller
2020-06-19 21:22 Conrad Kostecki
2020-06-17 16:18 Anthony G. Basile
2020-05-25 14:02 Conrad Kostecki
2020-05-25 11:17 Conrad Kostecki
2020-05-23 8:56 Michał Górny
2020-05-18 1:02 Michael Orlitzky
2020-04-15 0:35 Patrick McLean
2020-04-14 18:11 Robin H. Johnson
2020-04-10 10:46 Ulrich Müller
2020-04-02 11:13 Ulrich Müller
2020-03-17 13:14 Andreas K. Hüttel
2020-03-17 13:14 Andreas K. Hüttel
2020-02-15 22:37 James Le Cuirot
2020-02-11 17:22 Ulrich Müller
2020-01-25 11:17 Ulrich Müller
2020-01-17 9:10 Michał Górny
2019-12-25 20:48 Andreas K. Hüttel
2019-12-25 20:48 Andreas K. Hüttel
2019-12-05 23:32 Conrad Kostecki
2019-11-10 20:40 Michał Górny
2019-09-29 14:02 Pacho Ramos
2019-09-24 10:37 Ulrich Müller
2019-09-24 10:37 Ulrich Müller
2019-09-03 22:31 James Le Cuirot
2019-08-18 10:07 Michał Górny
2019-08-15 6:24 Michał Górny
2019-08-08 8:59 Ulrich Müller
2019-08-05 8:34 Ulrich Müller
2019-07-30 8:08 Michał Górny
2019-07-06 11:05 Ulrich Müller
2019-06-20 12:15 Ulrich Müller
2019-06-02 19:33 Stefan Strogin
2019-05-23 11:36 Ulrich Müller
2019-05-10 17:57 Patrick McLean
2019-05-02 22:05 Michał Górny
2019-04-15 8:00 Lars Wendler
2019-04-15 8:00 Lars Wendler
2019-01-22 19:11 Ulrich Müller
2018-12-23 12:50 Ulrich Müller
2018-12-11 16:20 Michał Górny
2018-12-11 16:20 Michał Górny
2018-12-07 16:16 Michał Górny
2018-11-28 11:31 Michał Górny
2018-11-28 11:31 Michał Górny
2018-11-16 23:01 Patrice Clement
2018-11-16 23:01 Patrice Clement
2018-10-22 20:14 Michał Górny
2018-10-18 10:54 James Le Cuirot
2018-09-13 17:19 Michał Górny
2018-09-13 16:14 Michał Górny
2018-09-13 16:14 Michał Górny
2018-09-13 16:14 Michał Górny
2018-08-25 19:22 Christian Ruppert
2018-08-24 19:40 Thomas Deutschmann
2018-08-05 13:57 Manuel Rüger
2018-07-11 11:17 Tony Vroon
2018-07-11 8:24 Tony Vroon
2018-06-26 19:02 Ben Kohler
2018-06-23 21:20 Ulrich Müller
2018-06-22 18:49 Michał Górny
2018-06-22 18:40 Michał Górny
2018-06-22 5:09 Ulrich Müller
2018-06-19 19:00 Michał Górny
2018-06-11 10:51 Ulrich Müller
2018-06-09 13:31 Ulrich Müller
2018-06-08 13:01 Alexey Shvetsov
2018-05-01 7:48 Michał Górny
2018-05-01 7:48 Michał Górny
2018-04-21 9:38 Ulrich Müller
2018-04-20 11:53 Michał Górny
2018-04-18 8:00 Michał Górny
2018-04-18 8:00 Michał Górny
2018-04-18 8:00 Michał Górny
2018-04-09 2:18 Tim Harder
2018-03-29 9:17 Michał Górny
2018-03-25 8:09 Michał Górny
2018-03-24 8:56 Michał Górny
2018-03-05 19:21 Ulrich Müller
2018-03-05 19:21 Ulrich Müller
2018-03-05 19:21 Ulrich Müller
2018-03-05 19:21 Ulrich Müller
2018-03-01 20:28 Jeroen Roovers
2018-01-23 20:06 Alfredo Tupone
2017-12-17 22:15 James Le Cuirot
2017-12-10 21:46 James Le Cuirot
2017-12-10 21:46 James Le Cuirot
2017-11-20 20:56 Alfredo Tupone
2017-11-19 20:48 Alfredo Tupone
2017-11-14 8:20 Ulrich Müller
2017-11-10 21:56 Ulrich Müller
2017-10-29 9:15 Ulrich Müller
2017-10-26 10:26 James Le Cuirot
2017-10-14 9:45 Ulrich Müller
2017-09-15 17:43 Patrick McLean
2017-09-06 6:42 Ulrich Müller
2017-09-06 6:41 Ulrich Müller
2017-08-30 19:14 Patrick McLean
2017-08-18 14:08 Ulrich Müller
2017-07-27 18:51 Sebastien Fabbro
2017-07-11 20:01 Michał Górny
2017-07-11 20:01 Michał Górny
2017-07-05 8:45 Michał Górny
2017-06-27 10:58 Marek Szuba
2017-05-17 16:22 William Hubbs
2017-05-16 17:11 Michał Górny
2017-05-07 17:36 Ulrich Müller
2017-04-27 21:41 James Le Cuirot
2017-04-27 21:41 James Le Cuirot
2017-04-27 21:41 James Le Cuirot
2017-04-24 7:53 Ulrich Müller
2017-04-20 9:06 Ulrich Müller
2017-04-19 19:46 Michał Górny
2017-04-19 14:46 Andreas Hüttel
2017-04-14 16:20 Ulrich Müller
2017-04-13 12:33 James Le Cuirot
2017-04-09 7:15 Ulrich Müller
2017-03-19 13:05 Ulrich Müller
2017-03-06 9:24 Mikhail Pukhlikov
2017-02-27 10:59 Ulrich Müller
2017-02-27 10:41 Ulrich Müller
2017-02-25 16:24 Ulrich Müller
2017-02-01 8:00 Ulrich Müller
2017-01-24 18:24 Ettore Di Giacinto
2017-01-14 17:22 Ulrich Müller
2016-12-29 4:12 Göktürk Yüksek
2016-12-17 13:33 José María Alonso
2016-12-01 12:33 José María Alonso
2016-12-01 0:08 Göktürk Yüksek
2016-12-01 0:08 Göktürk Yüksek
2016-12-01 0:08 Göktürk Yüksek
2016-12-01 0:08 Göktürk Yüksek
2016-11-13 9:56 Ulrich Müller
2016-11-12 1:14 Jonathan Vasquez
2016-10-27 9:28 Michał Górny
2016-10-27 9:28 Michał Górny
2016-10-18 16:59 Ulrich Müller
2016-10-12 10:18 Austin English
2016-10-11 7:49 David Seifert
2016-10-02 21:12 Ulrich Müller
2016-09-09 13:03 Wolfram Schlich
2016-08-12 20:41 Ulrich Müller
2016-08-12 20:41 Ulrich Müller
2016-08-12 19:33 Thomas Deutschmann
2016-08-12 19:33 Thomas Deutschmann
2016-06-25 10:24 Ulrich Müller
2016-06-19 17:38 Ulrich Müller
2016-05-20 15:05 Ulrich Müller
2016-05-20 14:11 Ulrich Müller
2016-05-20 13:24 Ian Delaney
2016-05-01 20:21 Ulrich Müller
2016-04-09 21:02 Andreas Hüttel
2016-04-07 22:39 Chí-Thanh Christopher Nguyễn
2016-03-24 12:57 Ulrich Müller
2016-03-19 21:32 Patrice Clement
2015-12-29 10:02 Justin Lecher
2015-12-27 10:08 Ian Delaney
2015-12-14 16:51 Richard Yao
2015-12-09 15:10 Justin Lecher
2015-11-29 3:35 Steve Arnold
2015-11-25 7:36 Ulrich Müller
2015-10-31 16:21 Ulrich Müller
2015-10-24 11:32 Alexis Ballier
2015-09-16 8:59 Justin Lecher
2015-09-16 8:53 Justin Lecher
2015-09-11 19:37 Patrice Clement
2015-09-07 12:31 Patrice Clement
2015-09-03 6:07 Justin Lecher
2015-08-27 22:59 Ulrich Müller
2015-08-19 23:16 Julian Ospald
2015-08-09 7:31 Ulrich Müller
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=1697821478.1570d79b8f41b7c28764866b68e86c78df48f2a8.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