From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/openrc:master commit in: etc/
Date: Sat, 5 Mar 2011 06:13:09 +0000 (UTC) [thread overview]
Message-ID: <0f3d6a01c7136edf1a7cecb764473ddc7f2cfe61.williamH@gentoo> (raw)
commit: 0f3d6a01c7136edf1a7cecb764473ddc7f2cfe61
Author: William Hubbs <williamh <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 5 06:11:24 2011 +0000
Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Sat Mar 5 06:11:24 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/openrc.git;a=commit;h=0f3d6a01
remove references to the migration guide
The openrc code base is not gentoo specific, so I feel that we should
not refer to the migration guide in the comments inside the configuration
files.
---
etc/rc.conf.FreeBSD | 1 -
etc/rc.conf.Linux | 1 -
etc/rc.conf.NetBSD | 1 -
3 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/etc/rc.conf.FreeBSD b/etc/rc.conf.FreeBSD
index 139a825..ed5b215 100644
--- a/etc/rc.conf.FreeBSD
+++ b/etc/rc.conf.FreeBSD
@@ -7,6 +7,5 @@
#
# This should be set to the value representing what environment this file is
# PRESENTLY in, not what virtualization the environment is capable of.
-# See the OpenRC migration guide for more details.
rc_sys="@RC_SYS_DEFAULT@"
diff --git a/etc/rc.conf.Linux b/etc/rc.conf.Linux
index 1400af5..9632a75 100644
--- a/etc/rc.conf.Linux
+++ b/etc/rc.conf.Linux
@@ -12,7 +12,6 @@
#
# This should be set to the value representing what environment this file is
# PRESENTLY in, not what virtualization the environment is capable of.
-# See the OpenRC migration guide for more details.
rc_sys="@RC_SYS_DEFAULT@"
##############################################################################
diff --git a/etc/rc.conf.NetBSD b/etc/rc.conf.NetBSD
index 3528a00..c49a9ab 100644
--- a/etc/rc.conf.NetBSD
+++ b/etc/rc.conf.NetBSD
@@ -8,6 +8,5 @@
#
# This should be set to the value representing what environment this file is
# PRESENTLY in, not what virtualization the environment is capable of.
-# See the OpenRC migration guide for more details.
rc_sys="@RC_SYS_DEFAULT@"
next reply other threads:[~2011-03-05 6:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 6:13 William Hubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-15 23:56 [gentoo-commits] proj/openrc:master commit in: etc/ William Hubbs
2016-09-28 0:40 William Hubbs
2016-07-20 21:44 William Hubbs
2016-07-20 21:44 William Hubbs
2015-12-02 17:12 William Hubbs
2015-10-29 16:36 William Hubbs
2015-05-22 14:57 William Hubbs
2015-05-08 17:33 William Hubbs
2014-12-08 1:07 William Hubbs
2014-08-11 18:18 William Hubbs
2014-08-22 19:10 ` William Hubbs
2014-03-15 3:19 William Hubbs
2014-03-09 20:39 William Hubbs
2013-12-08 19:45 William Hubbs
2013-03-12 19:18 William Hubbs
2013-02-17 17:09 William Hubbs
2013-02-16 22:12 William Hubbs
2012-12-04 0:24 William Hubbs
2012-10-30 16:17 William Hubbs
2012-02-13 18:00 William Hubbs
2012-01-25 18:40 Christian Ruppert
2012-01-06 4:36 William Hubbs
2011-11-26 23:47 William Hubbs
2011-07-06 23:40 William Hubbs
2011-07-05 22:52 Christian Ruppert
2011-04-18 20:22 William Hubbs
2011-03-22 4:05 William Hubbs
2011-03-15 3:11 William Hubbs
2011-03-03 21:07 William Hubbs
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=0f3d6a01c7136edf1a7cecb764473ddc7f2cfe61.williamH@gentoo \
--to=williamh@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