Re: [RFR] templates://git-stuff/{control,git-stuff.templates}
Christian PERRIER wrote:
> Quoting Justin B Rye (jbr@edlug.org.uk):
>> When should the cron job be started?
>
> Then you get a lintian warning..:-). We always recommended against
> interrogative form in long descriptions. So such sentences have to be
> turned in to "Please choose whether foobar" style
Oops, yes. "Please choose when the cron job should be started", and
drop the "Please" from the start of the next sentence.
Revised version attached.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru old/control new/control
--- old/control 2012-06-30 18:03:51.000000000 +0100
+++ new/control 2012-08-28 12:17:53.360411584 +0100
@@ -11,18 +11,15 @@
Depends: ${misc:Depends}, git
Recommends: cron, git-buildpackage, mr, pristine-tar
Description: additional Git utilities
- This is a growing collection of tools for the Git Version Control System.
- .
- Currently the following tools have been documented:
- .
- * git-amend-all: adds all untracked files and amend all changes to the last
- commit.
- * git-checkout-branches: checks out all remote branches.
- * git-cherry-pick-recursive: does a cherry-pick for a commit and each all its
- children.
- * git-commit-lazy: creates a new commit with all untracked files and changes.
- * git-debian-add: creates a new commit and tag with all untracked files and
- changes as new debian version.
- * git-debian-changelog: creates a new section in debian/changelog with all
- entries since the last release.
- * git-whoami: tells about author and committer information.
+ This is a growing collection of tools for the Git Version Control System,
+ including:
+ * git-amend-all
+ * git-checkout-branches
+ * git-cherry-pick-recursive
+ * git-commit-lazy
+ * git-{debian,progress}-{add,changelog,release,retag,tag}
+ * git-dpkg-source
+ * git-hook-notification-{bts,cia,cia.pl,email}
+ * git-repack-repositories{,-cron}
+ * git-upstream-{add,retag,tag,tar}
+ * git-whoami
diff -ru old/git-stuff.templates new/git-stuff.templates
--- old/git-stuff.templates 2012-06-30 18:04:05.000000000 +0100
+++ new/git-stuff.templates 2012-08-29 09:41:19.456411386 +0100
@@ -1,43 +1,39 @@
Template: git-repack-repositories/title
Type: title
-Description: Git Repack Repositories
+_Description: Git repack repositories
Template: git-repack-repositories/enable
Type: boolean
Default: false
-Description: Git repack:
- Git repositories tend to grow quite large quickly. From time to time, you
- have to repack the repositories to save space and keep optimal
- performances (by not having too many of files in the objects
- subdirectory).
- .
- Do you want to enable the cron job?
+_Description: Enable cron job?
+ Git repositories tend to grow quite large quickly. To save space and
+ maintain optimal performance they should be repacked from time to
+ time (reducing the number of files in the objects subdirectory).
Template: git-repack-repositories/directories
Type: string
Default: /srv/git
-Description: Git directories:
- Please specify the directory or directories (space separated) that is used
- as root for the Git repositories on your server. Note that
+_Description: Git directories:
+ Please specify the directory or directories (space separated) used
+ as root for the Git repositories on the server. Note that
git-repack-repositories will work recursively.
Template: git-repack-repositories/cron
Type: string
Default: @monthly
-Description: Git cron:
- What times should the cron job be started? Please refer to crontab(5) for
- the format definition. The default or if left empty will set the interval
- to '@monthly' (without the quotes) which means it gets executed every
- beginning of the month at midnight.
+_Description: Git cron job scheduling:
+ Please choose when the cron job should be started.
+ .
+ See crontab(5) for the format definition. If it is left empty, the
+ default value "@monthly" (without the quotes) will be used, executing
+ the cron job every month.
Template: git-stuff/title
Type: title
-Description: additional Git utilities
+_Description: Additional Git utilities
Template: git-stuff/bash-profile
Type: boolean
Default: false
-Description: Shortcuts for Bash (/etc/profile.d)
- Should special shortcut definitions for Bash be activated in /etc/profile.d?
- .
- If unsure, say no.
+_Description: Should shortcut definitions be activated?
+ Special shortcut definitions for Bash can be activated in /etc/profile.d.
Source: git-stuff
Section: misc
Priority: optional
Maintainer: Daniel Baumann <daniel.baumann@progress-technologies.net>
Uploaders: Andrew Lee (李健秋) <ajqlee@debian.org>
Build-Depends: debhelper (>= 8)
Standards-Version: 3.9.2
Package: git-stuff
Architecture: all
Depends: ${misc:Depends}, git
Recommends: cron, git-buildpackage, mr, pristine-tar
Description: additional Git utilities
This is a growing collection of tools for the Git Version Control System.
It includes:
* git-checkout-branches;
* git-debian-{add,changelog,release,retag,tag};
* git-dpkg-source;
* git-hook-notification-{bts,cia.pl,email};
* git-repack-repositories{,-cron};
* git-upstream-{add,retag,tag,tar}.
Template: git-repack-repositories/title
Type: title
_Description: Git Repack Repositories
Template: git-repack-repositories/enable
Type: boolean
Default: false
_Description: Automatically repack Git repositories?
Git repositories tend to grow quite large quickly, and need to be
repacked from time to time to save space and maintain performance
(by reducing overpopulation in the objects subdirectory). This can be
automated by use of a cron job.
.
Should the cron job be activated?
Template: git-repack-repositories/directories
Type: string
_Default: /srv/git
_Description: Git directories:
Please specify the directory (or directories, space separated) to be used
as root for the Git repositories on your server. Note that
git-repack-repositories will work recursively.
Template: git-repack-repositories/cron
Type: string
_Default: @monthly
_Description: Git cron schedule:
On what schedule should the cron job be started?
.
Please refer to crontab(5) for the format definition. If left empty the
default value "@monthly" will be used (without the quotes), executing
it during the night on the first of the month. (If the machine is likely
to be powered down, install anacron, which will run it close to this time.)
Reply to: