[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[shepherd] 03/32: Remove 'QUESTIONS' file.

From: Ludovic Courtès
Subject: [shepherd] 03/32: Remove 'QUESTIONS' file.
Date: Wed, 30 Mar 2022 11:01:27 -0400 (EDT)

civodul pushed a commit to branch master
in repository shepherd.

commit d13a18beb698b36c572168cad7471adb977d570c
Author: Ludovic Courtès <>
AuthorDate: Tue Mar 29 20:29:48 2022 +0200

    Remove 'QUESTIONS' file.
    * QUESTIONS: Remove.
    * (EXTRA_DIST): Remove it.
    * README: Adjust accordingly, and mention Git repository.
--- |  1 -
 QUESTIONS   | 25 -------------------------
 README      | 14 ++++++++------
 3 files changed, 8 insertions(+), 32 deletions(-)

diff --git a/ b/
index 774ebba..f8f9113 100644
--- a/
+++ b/
@@ -126,7 +126,6 @@ dist_man8_MANS = doc/halt.8 doc/reboot.8
 EXTRA_DIST +=                                  \
   build-aux/config.rpath                       \
   ChangeLog-2003                               \
-  QUESTIONS                                    \
   $(templates)                                 \
   doc/examples/README                          \
   doc/examples/_unknown.scm                    \
deleted file mode 100644
index b39e06f..0000000
+++ /dev/null
@@ -1,25 +0,0 @@
-Open questions about dmd
-- Do we need a `requests' field for services?  Service-symbols
-  specified there would be started like requirements, but if starting
-  all services providing it would fail, we could continue anyway.
-  This sounds nice, but it can easiely be emulated by adding to the
-  `start' code something like:
-    (for-each start '(service1 service2))
-  Since this is so simple, I wonder if this functionality is that
-  commonly needed that it is worth adding it.  If desired, it would be
-  trivial to implement if we don't consider that we might get into
-  trouble due to conflicts of these services with other services we
-  need to start.
-- Do we need a field for services that specifies the global startup
-  order, which has a smaller priority than dependencies?  This is
-  implemented in Darwins init system and was requested for dmd, but I
-  have no idea what that should be good for.  If desired, it would
-  probably not be extremely hard to hack it into dmd.  However, a
-  better solution might be soft dependencies: "If we start both FOO
-  and BAR, start FOO first."
diff --git a/README b/README
index 69647f3..7d777e4 100644
--- a/README
+++ b/README
@@ -42,13 +42,15 @@ should read the Texinfo manual for details:
 Detailed instructions on installing the GNU Shepherd are available in
 the file `INSTALL'.  A list of user-visible changes between releases can
-be found in the file `NEWS'.  Detailed information about changes on the
-source code level are listed in `ChangeLog'.  Open issues on which I
-would like to receive comments are explained in the file `QUESTIONS'.
+be found in the file `NEWS'.
-A list of people who can be considered maintainers of this software is
-available in the file `AUTHORS'.  A list of people who have been
-helpful in improving the Shepherd can be found in `THANKS'.
+See the Git version control history and the `AUTHORS' file for a list of
+people who contributed to this software:
+A list of people who have been helpful in improving the Shepherd can be
+found in `THANKS'.
 This program can be distributed under the terms of the GNU General
 Public License, version 3 or any later version, see the file `COPYING'

reply via email to

[Prev in Thread] Current Thread [Next in Thread]