public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: man/
Date: Sat, 11 Nov 2023 07:24:07 +0000 (UTC)	[thread overview]
Message-ID: <1699687442.dfc192ba206c334a388bebb7e8b046bed98c0101.sam@gentoo> (raw)

commit:     dfc192ba206c334a388bebb7e8b046bed98c0101
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 11 05:56:45 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 11 07:24:02 2023 +0000
URL:        https://gitweb.gentoo.org/proj/portage.git/commit/?id=dfc192ba

man: fix typos

Thanks to codespell.

Signed-off-by: Sam James <sam <AT> gentoo.org>

 man/color.map.5   |  6 +++---
 man/ebuild.5      |  8 ++++----
 man/emerge.1      | 10 +++++-----
 man/emirrordist.1 |  2 +-
 man/make.conf.5   |  6 +++---
 man/portage.5     | 14 +++++++-------
 6 files changed, 23 insertions(+), 23 deletions(-)

diff --git a/man/color.map.5 b/man/color.map.5
index eccb0c5a97..80446175d4 100644
--- a/man/color.map.5
+++ b/man/color.map.5
@@ -17,16 +17,16 @@ pattern]\fR
 .SH "VARIABLES"
 .TP
 \fBNORMAL\fR = \fI"normal"\fR
-Defines color used for some words occuring in other contexts than those below.
+Defines color used for some words occurring in other contexts than those below.
 .TP
 \fBBAD\fR = \fI"red"\fR
-Defines color used for some words occuring in bad context.
+Defines color used for some words occurring in bad context.
 .TP
 \fBBRACKET\fR = \fI"blue"\fR
 Defines color used for brackets.
 .TP
 \fBGOOD\fR = \fI"green"\fR
-Defines color used for some words occuring in good context.
+Defines color used for some words occurring in good context.
 .TP
 \fBHILITE\fR = \fI"teal"\fR
 Defines color used for highlighted words.

diff --git a/man/ebuild.5 b/man/ebuild.5
index cce5451755..aad189bb00 100644
--- a/man/ebuild.5
+++ b/man/ebuild.5
@@ -408,7 +408,7 @@ Contains the path to the directory in which package-specific auxiliary
 files are located.  Do not modify this variable.
 .TP
 .B EBUILD_PHASE
-Contains the abreviated name of the phase function that is
+Contains the abbreviated name of the phase function that is
 currently executing, such as "setup", "unpack", "compile", or
 "preinst".
 .TP
@@ -476,7 +476,7 @@ source	source\-build which is scheduled for merge
 .TP
 .B PROVIDES_EXCLUDE\fR = \fI[space delimited list of fnmatch patterns]\fR
 Sonames and file paths matched by these fnmatch patterns will be
-excluded during genertion of \fBPROVIDES\fR metadata (see
+excluded during generation of \fBPROVIDES\fR metadata (see
 \fBportage\fR(5)). Patterns are delimited by whitespace, and it is
 possible to create patterns containing quoted whitespace.
 .TP
@@ -553,7 +553,7 @@ Defines the ebuild API version to which this package conforms. If not
 defined then it defaults to "0". If portage does not recognize the
 EAPI value then it will mask the package and refuse to perform any
 operations with it since this means that a newer version of portage
-needs to be installed first. For maximum backward compatiblity, a
+needs to be installed first. For maximum backward compatibility, a
 package should conform to the lowest possible EAPI. Note that anyone
 who uses the \fBebuild\fR(1) command with this package will be
 required to have a version of portage that recognizes the EAPI to
@@ -961,7 +961,7 @@ end the function with a call to \fBdie\fR.
 .TP
 .B pkg_setup
 This function can be used if the package needs specific setup actions or
-checks to be preformed before anything else.
+checks to be performed before anything else.
 .br
 Initial working directory: $PORTAGE_TMPDIR
 .TP

diff --git a/man/emerge.1 b/man/emerge.1
index 667138ff3a..e18bc9e257 100644
--- a/man/emerge.1
+++ b/man/emerge.1
@@ -457,7 +457,7 @@ with resolving inconsistent USE flag settings, this option is
 automatically enabled unless the \fB\-\-usepkgonly\fR option
 is enabled. If \fB\-\-binpkg\-respect\-use\fR is given explicitly,
 then it implies \fB\-\-autounmask\-use=n\fR, because these options
-naturally oppose eachother.
+naturally oppose each other.
 .TP
 .BR "\-\-buildpkg [ y | n ]" ", " \-b
 Tells emerge to build binary packages for all ebuilds processed in
@@ -654,7 +654,7 @@ that can pull unbuilt ebuilds into the dependency graph, since unbuilt
 ebuilds do not have any soname dependency metadata, making it impossible
 to determine whether an unresolved soname dependency can be satisfied.
 Therefore, \fB\-\-usepkgonly\fR (or \fB\-\-getbinpkgonly\fR) must be
-used in order to enable soname depedency resolution when installing
+used in order to enable soname dependency resolution when installing
 packages.
 .TP
 .BR "\-\-ignore\-world [ y | n ]"
@@ -678,7 +678,7 @@ this option.
 Assume that packages may have implicit dependencies on packages which
 belong to the @system set. This option is enabled by default. One of the
 effects of disabling this option is to allow the \-\-jobs option to
-spawn jobs without accounting for the possiblity of implicit dependencies
+spawn jobs without accounting for the possibility of implicit dependencies
 on packages that belong to the @system set.
 .TP
 .BR \-j\ [JOBS] ", "  \-\-jobs[=JOBS]
@@ -931,7 +931,7 @@ mode whenever a new slot is installed. This option is enabled by
 default.
 
 NOTE: If you want to skip all rebuilds involving slot\-operator
-dependecies (including those that involve sub\-slot changes alone),
+dependencies (including those that involve sub\-slot changes alone),
 then \fI\-\-ignore\-built\-slot\-operator\-deps=y\fR is the option
 that you are looking for, since \fI\-\-rebuild\-if\-new\-slot\fR
 does not affect rebuilds triggered by sub\-slot changes alone.
@@ -1328,7 +1328,7 @@ permanent, you can put them in /etc/portage/package.use instead.
 If \fBemerge \-\-update @system\fR or \fBemerge \-\-update @world\fR
 fails with an error message, it may be that an ebuild uses some
 newer feature not present in this version of \fBemerge\fR.  You
-can use \fBemerge \-\-update sys-apps/portage\fR to upgrade to the lastest
+can use \fBemerge \-\-update sys-apps/portage\fR to upgrade to the latest
 version, which should support any necessary new features.
 .SH "MASKED PACKAGES"
 \fINOTE: Please use caution when using development packages.  Problems

diff --git a/man/emirrordist.1 b/man/emirrordist.1
index 37a56a8bb9..51b04c4885 100644
--- a/man/emirrordist.1
+++ b/man/emirrordist.1
@@ -21,7 +21,7 @@ Perform a trial run with no changes made (typically combined
 with \fI\-v\fR or \fI\-vv\fR).
 .TP
 \fB\-v\fR, \fB\-\-verbose\fR
-Display extra information on stderr (multiple occurences
+Display extra information on stderr (multiple occurrences
 increase verbosity).
 .TP
 \fB\-\-ignore\-default\-opts\fR

diff --git a/man/make.conf.5 b/man/make.conf.5
index 045882a17a..7e564c089f 100644
--- a/man/make.conf.5
+++ b/man/make.conf.5
@@ -332,7 +332,7 @@ should not be disabled by default.
 .RS
 .TP
 .B assume\-digests
-When commiting work to cvs with \fBrepoman\fR(1), assume that all existing
+When committing work to cvs with \fBrepoman\fR(1), assume that all existing
 SRC_URI digests are correct.  This feature also affects digest generation via
 \fBebuild\fR(1) and \fBemerge\fR(1) (emerge generates digests only when the
 \fIdigest\fR feature is enabled). Existing digests for files that do not exist
@@ -421,7 +421,7 @@ Enable a special progress indicator when \fBemerge\fR(1) is calculating
 dependencies.
 .TP
 .B case\-insensitive\-fs
-Use case\-insensitive file name comparisions when merging and unmerging
+Use case\-insensitive file name comparisons when merging and unmerging
 files. Most users should not enable this feature, since most filesystems
 are case\-sensitive. You should only enable this feature if you are
 using portage to install files to a case\-insensitive filesystem.
@@ -711,7 +711,7 @@ bits removed while files that are setgid have the other read bit removed.
 See also \fIsuidctl\fR below.
 .TP
 .B sign
-When commiting work to cvs with \fBrepoman\fR(1), sign the Manifest with
+When committing work to cvs with \fBrepoman\fR(1), sign the Manifest with
 a GPG key.  Read about the \fIPORTAGE_GPG_KEY\fR variable in
 \fBmake.conf\fR(5).
 .TP

diff --git a/man/portage.5 b/man/portage.5
index dae4d47206..d8990bf416 100644
--- a/man/portage.5
+++ b/man/portage.5
@@ -919,7 +919,7 @@ only.
 .BR repos.conf
 Specifies \fIsite\-specific\fR repository configuration information.
 .br
-Configuration specified in \fBrepos.conf\fR can be overriden by
+Configuration specified in \fBrepos.conf\fR can be overridden by
 \fBPORTAGE_REPOSITORIES\fR environmental variable, which has the same
 format as \fBrepos.conf\fR.
 
@@ -1106,12 +1106,12 @@ Extra options to give to mercurial when updating repository (hg pull).
 Enable read\-copy\-update (RCU) behavior for sync operations. The current
 latest immutable version of a repository will be referenced by a symlink
 found where the repository would normally be located (see the \fBlocation\fR
-setting). Repository consumers should resolve the cannonical path of this
+setting). Repository consumers should resolve the canonical path of this
 symlink before attempt to access the repository, and all operations should
 be read\-only, since the repository is considered immutable. Updates occur
 by atomic replacement of the symlink, which causes new consumers to use the
 new immutable version, while any earlier consumers continue to use the
-cannonical path that was resolved earlier. This option requires
+canonical path that was resolved earlier. This option requires
 sync\-allow\-hardlinks and sync\-rcu\-store\-dir options to be enabled, and
 currently also requires that sync\-type is set to rsync. This option is
 disabled by default, since the symlink usage would require special handling
@@ -1321,7 +1321,7 @@ sync\-uri = :pserver:anonymous@anoncvs.gentoo.org:/var/cvsroot
 sync\-cvs\-repo = gentoo\-x86
 auto\-sync = yes
 
-# Overlay 'voip' syncronized with layman's plug-in sync module
+# Overlay 'voip' synchronized with layman's plug-in sync module
 [voip]
 location = /var/lib/layman/voip
 sync\-type = laymanator
@@ -1646,7 +1646,7 @@ A list of all the packages which will be displayed when you run `emerge info`.
 A list of all the variables which will be displayed when you run `emerge info`.
 .TP
 .BR license_groups
-This contains groups of licenses that may be specifed in the
+This contains groups of licenses that may be specified in the
 \fBACCEPT_LICENSE\fR variable (see \fBmake.conf\fR(5)). Refer
 to GLEP 23 for further information:
 \fIhttps://www.gentoo.org/glep/glep-0023.html\fR.
@@ -1856,7 +1856,7 @@ all objects that the package installed onto your system.
 Contains information about the sonames that a package provides, which is
 automatically generated from the files that it installs. The sonames
 may have been filtered by the \fBPROVIDES_EXCLUDE\fR \fBebuild\fR(5)
-variable. A multilib category, followed by a colon, always preceeds a
+variable. A multilib category, followed by a colon, always precedes a
 list of one or more sonames.
 
 .I Example:
@@ -1870,7 +1870,7 @@ automatically generated from the files that it installs. The sonames
 may have been filtered by the \fBREQUIRES_EXCLUDE\fR \fBebuild\fR(5)
 variable. Any sonames that a package provides are automatically excluded
 from \fBREQUIRES\fR. A multilib category, followed by a colon, always
-preceeds a list of one or more sonames.
+precedes a list of one or more sonames.
 
 .I Example:
 .nf


             reply	other threads:[~2023-11-11  7:24 UTC|newest]

Thread overview: 278+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11  7:24 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-29 13:27 [gentoo-commits] proj/portage:master commit in: man/ Sam James
2025-03-29 13:22 Sam James
2025-03-29 13:22 Sam James
2024-08-20 16:30 Zac Medico
2024-08-15 17:28 Mike Gilbert
2024-05-26 19:12 Zac Medico
2024-05-13  5:43 Sam James
2024-04-28  0:04 Sam James
2024-03-28  4:26 Sam James
2023-12-18  5:30 John Helmert III
2023-10-11 18:34 Mike Gilbert
2023-10-06  1:30 Sam James
2023-09-16  5:50 Sam James
2023-09-16  5:48 Sam James
2023-08-08  4:51 Sam James
2023-04-07  9:52 Sam James
2023-04-07  6:41 Ulrich Müller
2023-04-07  6:41 Ulrich Müller
2023-02-26 21:55 Sam James
2023-02-26 21:55 Sam James
2023-02-15  5:49 Sam James
2023-01-14 16:41 Sam James
2022-12-21  1:28 Sam James
2022-10-10 19:49 Sam James
2022-10-10 19:49 Sam James
2022-10-10 19:49 Sam James
2022-10-10 19:49 Sam James
2022-08-12 16:07 Zac Medico
2022-07-20  3:44 Sam James
2022-07-20  3:44 Sam James
2022-07-20  3:38 Sam James
2022-07-20  2:09 Sam James
2022-07-20  2:09 Sam James
2022-07-20  2:09 Sam James
2022-07-19  0:18 Sam James
2022-07-18 20:22 Sam James
2022-07-18 20:14 Sam James
2022-07-18 20:14 Sam James
2022-07-18 19:37 Sam James
2022-07-18 19:37 Sam James
2022-07-18 19:37 Sam James
2022-07-18 19:37 Sam James
2022-07-18 19:37 Sam James
2022-04-24 21:47 Zac Medico
2021-08-15 20:58 Sam James
2021-07-04 23:00 Zac Medico
2021-05-24  6:47 Zac Medico
2021-04-25  3:39 Zac Medico
2021-04-25  3:39 Zac Medico
2021-04-05 20:42 Zac Medico
2021-03-06  8:41 Zac Medico
2021-02-27  7:56 Zac Medico
2021-02-22 12:31 Zac Medico
2021-02-01 18:08 Zac Medico
2021-01-18 18:20 Ulrich Müller
2020-09-08  1:17 Zac Medico
2020-09-07 23:41 Zac Medico
2020-09-06  1:14 Zac Medico
2020-07-07 20:15 Zac Medico
2020-06-30 19:15 Mike Frysinger
2020-03-14 19:02 Zac Medico
2019-11-27  3:19 Zac Medico
2019-11-21 20:11 Zac Medico
2019-10-12  7:26 Michał Górny
2019-09-29 21:51 Zac Medico
2019-09-11  9:49 Mike Frysinger
2019-09-01 22:11 Zac Medico
2019-09-01 19:03 Zac Medico
2019-09-01  4:59 Zac Medico
2019-08-31  3:44 Zac Medico
2019-08-26 18:13 Zac Medico
2019-07-29  8:54 Ulrich Müller
2019-07-29  8:54 Ulrich Müller
2019-07-10 20:26 Zac Medico
2019-06-19 21:19 Zac Medico
2019-03-17 20:49 Zac Medico
2019-03-17 20:49 Zac Medico
2019-03-17 20:31 Zac Medico
2018-12-20 23:10 Mike Frysinger
2018-12-20  4:29 Zac Medico
2018-10-02 17:20 Mike Frysinger
2018-08-29 18:17 Zac Medico
2018-05-01 16:26 Zac Medico
2018-04-13 21:13 Zac Medico
2018-01-13 10:11 Zac Medico
2018-01-13 10:11 Zac Medico
2018-01-09 18:49 Mike Frysinger
2018-01-09 18:49 Mike Frysinger
2018-01-09 18:49 Mike Frysinger
2017-10-24 10:35 Ulrich Müller
2017-10-14 20:47 Ulrich Müller
2017-10-09 18:25 Manuel Rüger
2017-05-30  9:57 Zac Medico
2017-04-22  7:56 Zac Medico
2017-02-28 20:39 Zac Medico
2017-01-26 18:49 Zac Medico
2017-01-08 23:44 Zac Medico
2016-12-14 21:05 Zac Medico
2016-02-02 20:46 Alexander Berntsen
2015-11-25  0:05 Mike Frysinger
2015-09-22 16:40 Brian Dolbec
2015-09-20  2:27 Brian Dolbec
2015-09-20  2:27 Brian Dolbec
2015-07-20 21:48 Brian Dolbec
2015-06-18 12:27 Alexander Berntsen
2015-05-30 18:34 Brian Dolbec
2015-05-19 10:54 Alexander Berntsen
2015-05-18 23:19 Brian Dolbec
2015-05-18 23:19 Brian Dolbec
2015-03-04 20:39 Brian Dolbec
2015-03-04 20:39 Brian Dolbec
2015-02-28 17:34 Pavel Kazakov
2015-02-26  6:33 Mike Frysinger
2015-02-24  0:38 Zac Medico
2015-02-18 18:24 Mike Frysinger
2015-02-08 17:41 [gentoo-commits] proj/portage:v2.2.16 " Brian Dolbec
2015-02-08 17:40 ` [gentoo-commits] proj/portage:master " Brian Dolbec
2015-02-08 17:41 [gentoo-commits] proj/portage:v2.2.16 " Brian Dolbec
2015-02-05 21:16 ` [gentoo-commits] proj/portage:master " Brian Dolbec
2015-02-06 19:46 Brian Dolbec
2015-02-04 21:54 [gentoo-commits] proj/portage:v2.2.16 " Brian Dolbec
2015-02-04 21:53 ` [gentoo-commits] proj/portage:master " Brian Dolbec
2015-01-24 17:40 Michał Górny
2015-01-05 20:09 Zac Medico
2015-01-05 20:02 Zac Medico
2014-12-08 15:38 Zac Medico
2014-11-10 18:33 Zac Medico
2014-07-19 13:51 Alexander Berntsen
2014-06-14 21:55 Alexander Berntsen
2014-04-18 21:15 Arfrever Frehtes Taifersar Arahesis
2014-03-14 10:33 Alexander Berntsen
2014-03-02  8:46 Brian Dolbec
2014-01-23  1:07 Mike Frysinger
2014-01-23  1:06 Mike Frysinger
2014-01-08 13:43 Arfrever Frehtes Taifersar Arahesis
2014-01-05 22:23 Mike Frysinger
2014-01-05 19:09 Mike Frysinger
2013-12-03 15:26 Arfrever Frehtes Taifersar Arahesis
2013-12-02 15:14 Arfrever Frehtes Taifersar Arahesis
2013-12-02  1:23 Brian Dolbec
2013-12-02  1:23 Brian Dolbec
2013-08-12 22:40 Zac Medico
2013-08-12 22:22 Zac Medico
2013-08-12 22:20 Zac Medico
2013-08-12 22:14 Zac Medico
2013-08-12  2:33 Zac Medico
2013-08-11 22:30 Zac Medico
2013-08-08 17:11 Zac Medico
2013-07-31 21:59 Zac Medico
2013-07-30 23:09 Zac Medico
2013-07-30 23:04 Zac Medico
2013-07-30 22:45 Zac Medico
2013-07-30 19:13 Zac Medico
2013-07-30 19:13 Zac Medico
2013-07-25 22:43 Zac Medico
2013-07-24 21:22 Zac Medico
2013-07-23 22:52 Arfrever Frehtes Taifersar Arahesis
2013-07-22 19:20 Zac Medico
2013-07-22  4:44 Arfrever Frehtes Taifersar Arahesis
2013-07-06 19:24 Zac Medico
2013-06-24  9:30 Arfrever Frehtes Taifersar Arahesis
2013-06-18 17:57 Zac Medico
2013-06-18 16:35 Zac Medico
2013-06-13  0:14 Zac Medico
2013-06-09 23:30 Zac Medico
2013-05-24  2:23 Zac Medico
2013-05-17 16:08 Zac Medico
2013-05-15 21:23 Zac Medico
2013-05-01 21:05 Zac Medico
2013-04-24  3:51 Zac Medico
2013-04-23  3:20 Zac Medico
2013-04-08  0:32 Zac Medico
2013-04-04 16:48 Zac Medico
2013-04-04 14:23 Zac Medico
2013-04-03  3:12 Zac Medico
2013-04-02 19:57 Mike Frysinger
2013-03-24 19:23 Zac Medico
2013-03-23 19:45 Zac Medico
2013-03-01  3:40 Mike Frysinger
2013-02-01  2:33 Zac Medico
2013-01-30 16:32 Zac Medico
2013-01-30 16:04 Zac Medico
2013-01-28 21:03 Mike Frysinger
2013-01-21 16:52 Zac Medico
2013-01-15 22:42 Mike Frysinger
2013-01-15 21:44 Zac Medico
2013-01-15 11:10 Zac Medico
2013-01-11  8:08 Zac Medico
2013-01-10  7:17 Zac Medico
2012-12-28 21:44 Zac Medico
2012-12-28 21:36 Zac Medico
2012-12-28 21:22 Zac Medico
2012-11-28 12:14 Zac Medico
2012-10-14 21:38 Zac Medico
2012-09-25 17:29 Zac Medico
2012-09-25 16:50 Zac Medico
2012-09-25 16:50 Zac Medico
2012-09-25 16:50 Zac Medico
2012-09-25  2:19 Zac Medico
2012-09-24 21:43 Zac Medico
2012-09-24 21:01 Zac Medico
2012-09-24 20:28 Zac Medico
2012-09-24 20:28 Zac Medico
2012-09-24  2:44 Zac Medico
2012-09-24  2:44 Zac Medico
2012-09-24  2:44 Zac Medico
2012-09-24  2:44 Zac Medico
2012-09-24  2:44 Zac Medico
2012-09-24  2:44 Zac Medico
2012-09-22 17:08 Zac Medico
2012-09-21 21:51 Zac Medico
2012-09-16 18:59 Zac Medico
2012-09-16 18:24 Zac Medico
2012-09-16 18:13 Zac Medico
2012-09-16 17:47 Zac Medico
2012-09-15 20:54 Zac Medico
2012-09-15 20:43 Zac Medico
2012-09-15 20:27 Zac Medico
2012-09-15 19:58 Zac Medico
2012-09-15 19:53 Zac Medico
2012-09-15 19:39 Zac Medico
2012-09-15 19:26 Zac Medico
2012-09-15 19:12 Zac Medico
2012-09-15 19:09 Zac Medico
2012-09-14 18:10 Zac Medico
2012-09-04  1:06 Zac Medico
2012-08-22 20:36 Zac Medico
2012-08-19 21:34 Zac Medico
2012-08-05 20:35 Zac Medico
2012-07-20 20:16 Zac Medico
2012-07-10  5:42 Mike Frysinger
2012-06-30 20:51 Zac Medico
2012-06-29 20:41 Mike Frysinger
2012-06-23  0:45 Zac Medico
2012-06-23  0:29 Zac Medico
2012-06-02  3:05 Zac Medico
2012-06-01  3:16 Mike Frysinger
2012-05-08 16:38 Zac Medico
2012-04-13 18:30 Zac Medico
2012-03-30  0:17 Zac Medico
2012-03-08 23:26 Mike Frysinger
2012-02-17 23:33 Zac Medico
2012-01-21  4:01 Zac Medico
2012-01-20  4:46 Zac Medico
2012-01-02 23:01 Zac Medico
2011-12-24 11:30 Zac Medico
2011-12-22 23:57 Arfrever Frehtes Taifersar Arahesis
2011-12-21 19:37 Zac Medico
2011-12-16 20:55 Zac Medico
2011-12-15 18:49 Zac Medico
2011-12-15 18:04 Zac Medico
2011-12-07 19:21 Zac Medico
2011-11-30 20:27 Mike Frysinger
2011-11-21 15:00 Zac Medico
2011-10-29  8:16 Zac Medico
2011-10-29  8:11 Zac Medico
2011-10-27  4:43 Zac Medico
2011-10-26 22:00 Zac Medico
2011-10-23 21:13 Zac Medico
2011-10-21  8:51 Zac Medico
2011-10-17  2:56 Zac Medico
2011-10-16 19:44 Zac Medico
2011-10-14 14:56 Zac Medico
2011-10-13  2:51 Mike Frysinger
2011-09-23 17:56 Zac Medico
2011-09-13  6:07 Zac Medico
2011-08-31 18:14 Zac Medico
2011-08-22 20:36 Zac Medico
2011-07-08 16:57 Zac Medico
2011-07-07  8:10 Zac Medico
2011-06-19 19:44 Zac Medico
2011-06-09 22:08 Zac Medico
2011-05-30 22:27 Zac Medico
2011-05-26 18:35 Zac Medico
2011-02-22 17:58 Zac Medico
2011-02-22 17:31 Zac Medico
2011-02-22  2:21 Zac Medico
2011-02-13  8:58 Zac Medico
2011-02-08 19:55 Zac Medico
2011-02-07 21:26 Zac Medico

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=1699687442.dfc192ba206c334a388bebb7e8b046bed98c0101.sam@gentoo \
    --to=sam@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