[pkgsrc/trunk]: pkgsrc/doc/guide/files The guide currently contains a mix of ...

[sevan <sevan%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/753b621b8162
branches:  trunk
changeset: 353744:753b621b8162
user:      sevan <sevan%pkgsrc.org@localhost>
date:      Tue Oct 11 15:41:09 2016 +0000

description:
The guide currently contains a mix of csh & bourne style examples, acknowledge that until docs are amended to a single syntax.
Discussed long ago but forgot to commit diff.

diffstat:

 doc/guide/files/introduction.xml |  7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diffs (20 lines):

diff -r 8624e5682c40 -r 753b621b8162 doc/guide/files/introduction.xml
--- a/doc/guide/files/introduction.xml  Tue Oct 11 14:39:13 2016 +0000
+++ b/doc/guide/files/introduction.xml  Tue Oct 11 15:41:09 2016 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: introduction.xml,v 1.38 2016/06/11 14:58:26 rillig Exp $ -->
+<!-- $NetBSD: introduction.xml,v 1.39 2016/10/11 15:41:09 sevan Exp $ -->
 
 <chapter id="introduction">
   <title>What is pkgsrc?</title>
@@ -388,7 +388,8 @@
     <para>When giving examples for commands, shell prompts are used to
       show if the command should/can be issued as root, or if
       <quote>normal</quote> user privileges are sufficient. We use a
-      &rprompt; for root's shell prompt, and a &cprompt; for users'
-      shell prompt, assuming they use the C-shell or tcsh.</para>
+      &rprompt; for root's shell prompt, a &cprompt; for users'
+      shell prompt, assuming they use the C-shell or tcsh and a &uprompt for
+      bourne shell and derivatives.</para>
   </sect1>
 </chapter>