summaryrefslogtreecommitdiff
path: root/docs/example_hook
diff options
context:
space:
mode:
authormaximilian attems <maks@debian.org>2006-07-16 21:54:14 +0200
committermaximilian attems <maks@debian.org>2006-07-16 21:54:14 +0200
commit17d01b3434dac54ace5991029ed069b3d185ffd2 (patch)
treec31f2ca8f0ca57242e7db41ef1bf12c86cc97fa6 /docs/example_hook
parent8e9ecf2b5f9ced135e29d12fbe53c727a248934d (diff)
massif whitespace cleanup
Diffstat (limited to 'docs/example_hook')
-rw-r--r--docs/example_hook6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/example_hook b/docs/example_hook
index de5392d..a0d015a 100644
--- a/docs/example_hook
+++ b/docs/example_hook
@@ -12,7 +12,7 @@
# added to the initramfs, but the linux-image it relates to has
# already been installed previously? Does this happen often
# enough that it needs to be handled? How can it be handled?
-#
+#
# * Think about the 'usplash'. The initramfs will need to be
# updated if a theme change or update is desired. Maybe it
# should not be totally automatic, but offered on upgrade
@@ -96,9 +96,9 @@ fi
#
if [ -n "$an_error_occured" ];
then
- #
+ #
# TODO: Do we need 'warn()', 'error()', and/or 'fatal()' for this?
- #
+ #
echo "An error occured in $0: $an_error_occured" >&2
exit 1
#