From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/sudo
Date: Wed, 27 Aug 2008 13:18:45 -0700 (PDT) [thread overview]
Message-ID: <20080827201845.1767F3C831@busybox.net> (raw)
Author: jacmet
Date: 2008-08-27 13:18:43 -0700 (Wed, 27 Aug 2008)
New Revision: 23250
Log:
sudo: fix long help text lines
Modified:
trunk/buildroot/package/sudo/Config.in
Changeset:
Modified: trunk/buildroot/package/sudo/Config.in
===================================================================
--- trunk/buildroot/package/sudo/Config.in 2008-08-27 20:18:40 UTC (rev 23249)
+++ trunk/buildroot/package/sudo/Config.in 2008-08-27 20:18:43 UTC (rev 23250)
@@ -1,7 +1,7 @@
config BR2_PACKAGE_SUDO
bool "sudo"
help
- Sudo is a program designed to allow a sysadmin to give limited root
- privileges to users and log root activity. The basic philosophy is to give
- as few privileges as possible but still allow people to get their work done.
-
+ Sudo is a program designed to allow a sysadmin to give
+ limited root privileges to users and log root activity. The
+ basic philosophy is to give as few privileges as possible
+ but still allow people to get their work done.
next reply other threads:[~2008-08-27 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 20:18 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-12 0:06 [Buildroot] svn commit: trunk/buildroot/package/sudo ulf at uclibc.org
2009-01-12 6:27 ` Peter Korsgaard
2009-01-12 8:42 ` Ulf Samuelsson
2009-01-12 9:01 ` Peter Korsgaard
2009-01-11 22:31 ulf at uclibc.org
2009-01-11 20:36 jacmet at uclibc.org
2009-01-11 22:24 ` Ulf Samuelsson
2009-01-12 6:26 ` Peter Korsgaard
2009-01-11 19:58 ulf at uclibc.org
2008-03-06 18:26 ninevoltz at uclibc.org
2006-12-21 13:52 aldot at uclibc.org
2006-12-15 15:15 aldot at uclibc.org
2006-10-03 13:42 aldot at uclibc.org
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=20080827201845.1767F3C831@busybox.net \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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