From: "Priit Laes" <plaes@plaes.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-keyring/
Date: Thu, 6 Oct 2011 05:22:14 +0000 (UTC) [thread overview]
Message-ID: <1f78cc62f4ddda3890c6f78a248b5de6195b3edf.plaes@gentoo> (raw)
commit: 1f78cc62f4ddda3890c6f78a248b5de6195b3edf
Author: Priit Laes <plaes <AT> plaes <DOT> org>
AuthorDate: Thu Oct 6 05:14:32 2011 +0000
Commit: Priit Laes <plaes <AT> plaes <DOT> org>
CommitDate: Thu Oct 6 05:17:23 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=1f78cc62
gnome-base/gnome-keyring: fixed typo in Flameeyes' nick
---
.../gnome-keyring/gnome-keyring-3.2.0-r1.ebuild | 2 +-
gnome-base/gnome-keyring/gnome-keyring-9999.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnome-base/gnome-keyring/gnome-keyring-3.2.0-r1.ebuild b/gnome-base/gnome-keyring/gnome-keyring-3.2.0-r1.ebuild
index f0f0572..9be61bb 100644
--- a/gnome-base/gnome-keyring/gnome-keyring-3.2.0-r1.ebuild
+++ b/gnome-base/gnome-keyring/gnome-keyring-3.2.0-r1.ebuild
@@ -81,7 +81,7 @@ pkg_postinst() {
gnome2_pkg_postinst
}
-# borrowed from GSoC2010_Gentoo_Capabilities by constanze and flameyeys
+# borrowed from GSoC2010_Gentoo_Capabilities by constanze and Flameeyes
# @FUNCTION: fcaps
# @USAGE: fcaps {uid:gid} {file-mode} {cap1[,cap2,...]} {file}
# @RETURN: 0 if all okay; non-zero if failure and fallback
diff --git a/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild b/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild
index f0f0572..9be61bb 100644
--- a/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild
+++ b/gnome-base/gnome-keyring/gnome-keyring-9999.ebuild
@@ -81,7 +81,7 @@ pkg_postinst() {
gnome2_pkg_postinst
}
-# borrowed from GSoC2010_Gentoo_Capabilities by constanze and flameyeys
+# borrowed from GSoC2010_Gentoo_Capabilities by constanze and Flameeyes
# @FUNCTION: fcaps
# @USAGE: fcaps {uid:gid} {file-mode} {cap1[,cap2,...]} {file}
# @RETURN: 0 if all okay; non-zero if failure and fallback
next reply other threads:[~2011-10-06 5:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 5:22 Priit Laes [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-12 12:46 [gentoo-commits] proj/gnome:master commit in: gnome-base/gnome-keyring/ Dennis Lamm
2016-03-26 22:54 Ole Reifschneider
2015-05-10 17:20 Gilles Dartiguelongue
2014-12-22 23:11 Gilles Dartiguelongue
2014-10-26 15:46 Gilles Dartiguelongue
2014-04-16 22:27 Gilles Dartiguelongue
2014-02-12 20:58 Gilles Dartiguelongue
2013-12-11 23:44 Gilles Dartiguelongue
2013-10-13 22:22 Gilles Dartiguelongue
2012-12-17 8:14 Gilles Dartiguelongue
2012-11-25 15:46 Gilles Dartiguelongue
2012-10-24 8:10 Alexandre Rostovtsev
2012-09-27 22:32 Alexandre Rostovtsev
2012-09-22 15:54 Nirbheek Chauhan
2012-09-05 15:48 Nirbheek Chauhan
2012-05-14 6:38 Alexandre Restovtsev
2012-04-20 7:29 Alexandre Restovtsev
2012-03-26 8:20 Nirbheek Chauhan
2012-02-27 2:24 Alexandre Restovtsev
2011-10-21 4:01 Alexandre Restovtsev
2011-10-18 7:37 Alexandre Restovtsev
2011-10-05 21:41 Alexandre Restovtsev
2011-05-28 3:40 Gilles Dartiguelongue
2011-04-11 22:25 Gilles Dartiguelongue
2011-04-10 18:04 Gilles Dartiguelongue
2011-04-05 0:57 Nirbheek Chauhan
2011-02-15 23:45 Nirbheek Chauhan
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=1f78cc62f4ddda3890c6f78a248b5de6195b3edf.plaes@gentoo \
--to=plaes@plaes.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