apt/po, branch 1.1.2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.22015-11-28T21:49:07ZRelease 1.1.22015-11-28T21:49:07ZJulian Andres Klodejak@debian.org2015-11-28T21:49:07Zurn:sha1:20597fb843c52cddd108ebfb50108ccb662b687aRun ./prepare-release pre-export2015-11-25T15:06:02ZMichael Vogtmvo@ubuntu.com2015-11-25T15:04:35Zurn:sha1:9270be361451829fec7e4c9acc2ff2bca47e82d5review of new/changed translatable program strings2015-11-21T17:04:29ZJustin B Ryejustin.byam.rye@gmail.com2015-11-21T16:50:06Zurn:sha1:d04e44ac8177fc5b70ae0189bb5e437c2502f910
Reference mail:
https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
more sensible default text in pot files2015-11-19T16:13:56ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-19T16:12:32Zurn:sha1:12f7536a66cab673833aeda47be5f2ba44aee8d2
Git-Dch: Ignore
revamp all tools help messages2015-11-04T17:04:05ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-27T08:57:26Zurn:sha1:8561c2fedae26aecd8ba758a5e7ef686ba1243f3
The general idea is: A small paragraph on the tool itself as a
description, a list of the most used (!= all) commands available in the
tool, a remark where to find more information on the tool and its
commands (aka: in the manpage) and finally a common block referring to
even more manpages. In exchange options are completely omitted from the
output as well as deprecated or obscure commands. (Better) Information
about them is available in the manpages anyway and the few options which
were listed before were also the least interesting ones (-o -c -q and co
are hardly of interest for someone totally new looking to find info by
asking for help and anyone with a bit of experience doesn't need this
short list. Those would need a list of options applying to the command
they call, but they are too numerous and command specific to list them
sanely in this context.
split up help messages for simpler reuse2015-11-04T17:04:03ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-22T14:28:54Zurn:sha1:cbbee23e7768750ca1c8b49bdfbf8a650131bbb6
That is one huge commit with busy work only: Help messages used to be
one big translateable string, which is a pain for translators and hard
to reuse for us. This change there 'explodes' this single string into
new string for each documented string trying hard to split up the
translated messages as well. This actually restores many translations as
previously adding a single command made all of the bug message fuzzy.
The splitup also highlighted that its easy to forget a line, duplicate
one and similar stuff.
Git-Dch: Ignore
suggest 'apt autoremove' to get right of unneeded packages2015-11-04T17:04:01ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-16T10:54:14Zurn:sha1:73fe49f9b4748eddb5a2dad4f0abb51a8f63564c
The bugreport is more conservative in asking for a conditional, but
given that this is a message intended to be read by users to be run by
users we should suggest using a command intended to be used by users.
And while we are at, add sudo to the message – conditional of course.
Closes: 801571
Turkish program translation update2015-11-04T14:02:36ZMert Dirikmertdirik@gmail.com2015-10-22T13:43:58Zurn:sha1:f9ed8466916776f19e4b2be113082f6e238f543a
Closes: 802610
Run "./prepare-release pre-export"2015-10-05T16:30:19ZMichael Vogtmvo@ubuntu.com2015-10-05T16:30:19Zurn:sha1:04f27faefbd3b86e069b2fe3d964a56f61afda0d
Git-dch: ignore
Use --add-location=file for po/ and doc/po2015-09-22T14:56:34ZMichael Vogtmvo@ubuntu.com2015-09-22T14:56:34Zurn:sha1:9a2902305b75a6bc5a288fd1b12323c77df09b8c
This avoids churn in the po/pot files when just the location line
number in the source code changes.
Git-Dch: ignore