From: Nikita Karetnikov <nikita@karetnikov.org>
To: bug-guix@gnu.org
Subject: [PATCH] gnu: ddrescue: Fix 'synopsis' and 'description'.
Date: Fri, 18 Jan 2013 02:30:50 -0500 [thread overview]
Message-ID: <87bocnuev5.fsf@karetnikov.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 101 bytes --]
Hi,
There was a mistake in 'description'. I fixed it and also changed a
couple of things.
Nikita
[-- Attachment #1.2: 0001-gnu-ddrescue-Fix-synopsis-and-description.patch --]
[-- Type: text/x-diff, Size: 2673 bytes --]
From 1691be7ff5f0484d503eeb5016d2e0c77c4f0afd Mon Sep 17 00:00:00 2001
From: Nikita Karetnikov <nikita@karetnikov.org>
Date: Fri, 18 Jan 2013 07:27:06 +0000
Subject: [PATCH] gnu: ddrescue: Fix 'synopsis' and 'description'.
* gnu/packages/ddrescue.scm (ddrescue): Fix 'synopsis' and 'description'.
---
gnu/packages/ddrescue.scm | 21 +++++++++------------
1 files changed, 9 insertions(+), 12 deletions(-)
diff --git a/gnu/packages/ddrescue.scm b/gnu/packages/ddrescue.scm
index e9c7856..0d5533d 100644
--- a/gnu/packages/ddrescue.scm
+++ b/gnu/packages/ddrescue.scm
@@ -1,5 +1,5 @@
;;; GNU Guix --- Functional package management for GNU
-;;; Copyright © 2012 Nikita Karetnikov <nikita@karetnikov.org>
+;;; Copyright © 2012, 2013 Nikita Karetnikov <nikita@karetnikov.org>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -37,24 +37,21 @@
(build-system gnu-build-system)
(home-page
"http://www.gnu.org/software/ddrescue/ddrescue.html")
- (synopsis "GNU ddrescue, a data recovery tool")
+ (synopsis "GNU Ddrescue, a data recovery tool")
(description
- "GNU ddrescue is a data recovery tool. It copies data from one
-file or block device (hard disc, cdrom, etc) to another, trying hard to
+ "GNU Ddrescue is a data recovery tool. It copies data from one
+file or block device (e.g., hard disk, CD-ROM) to another, trying hard to
rescue data in case of read errors.
-The basic operation of ddrescue is fully automatic. That is, you don't
+The basic operation of Ddrescue is fully automatic. That is, you don't
have to wait for an error, stop the program, read the log, run it in
reverse mode, etc.
-If you use the logfile feature of ddrescue, the data is rescued very
-efficiently (only the needed blocks are read). Also you can interrupt
+If you use the logfile feature of Ddrescue, the data is rescued very
+efficiently (only the needed blocks are read). Also, you can interrupt
the rescue at any time and resume it later at the same point.
Automatic merging of backups: If you have two or more damaged copies of
-a file, cdrom, etc, and run ddrescue on all of them, one at a time, with
-the same output file, you will probably obtain a complete and error-free
-file. This is so because the probability of having damaged areas at the
-same places on different input files is very low. Using the logfile,
-only the needed blocks are read from the second and successive copies.")
+a file and run Ddrescue on all of them, one at a time, with the same
+output file, you will probably obtain a complete and error-free file.")
(license gpl3+)))
--
1.7.5.4
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next reply other threads:[~2013-01-18 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 7:30 Nikita Karetnikov [this message]
2013-01-18 13:12 ` [PATCH] gnu: ddrescue: Fix 'synopsis' and 'description' Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bocnuev5.fsf@karetnikov.org \
--to=nikita@karetnikov.org \
--cc=bug-guix@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).