Hi Helge, On 19/11/2011 09:48, Helge Kreutzmann wrote: > On Tue, Nov 08, 2011 at 12:56:23PM -0400, David Prévot wrote: >> Fine for me, I think other active po4a contributors are following the >> BTS too, I just CCed the po4a upstream developers list to make sure of >> that. For future typos, providing an actual patch[es serie] one could >> review and acknowledge directly would be even more welcome, you may send >> them directly to <po4a-de...@lists.alioth.debian.org> (it's a low >> traffic list you may consider subscribing to). > > I just checked in a new version (which seems to have caused a > problem[1]?) and have found some more typos/improvement possibilites. > However, this raises two problems: > > a) Often I would like to explain the change (e.g. "I'm unsure" or > "merge with" or ...), how should I do this in the patch?
That's the beauty with patches series: it's possible to actually prepare atomic commits, with one change by commit, and a meaningful commit message for each change. Other people can then acknowledge (or not) the whole series, or each individual commit, eventual amending those some of them, making quite easy the task to apply them ones agreed. That's actually one of the reason why I use “git svn”: it allows to prepare the changes, eventually reorder them (and even merge similar ones) with “git rebase -i”, and propose them (or directly commit them as I did with your previous proposals I had no doubt with). It makes it easier to revert a specific commit if someone disagrees afterward too. You can then prepare the patch series with “git format-patch” and send them directly to the list or the bug report with “git send-email” (no attachment needed ;-). [ I must admit that I'm still discovering Git, which seems like a pretty efficient toy, and I can't stop playing with it. ] Even after a simple “svn diff > fixes.patch”, one can add comments in the mail or bug report, quoting part or all of the diff in the message, and also attach the file in order to ease the reviewing process. I guess you could even prepare a review branch in the po4a tree (I did something like that a year ago, when I prepared a huge review of typographic and convention stuff of the documentation). > I'm not > sure I can dig out all commenting methods properly? Do you think > keeping the previous style would be possible? I'm not sure I understood, could you please rephrase? > b) As upstream is using an e-mail list on alioth, I cannot mail them > (cf. bug #582765, hopefully the maintainer of courier-mta somewhen > talks to me :-((). Wow, that's annoying (glad to use Dovecot on my servers, It seems like I'm not the only one [0]), I'm surprised to discover this issue only now: if Alioth is affected, a lot of people might be in a black hole… I guess you can always send unsigned mails without attachment, and eventually provide an URL to the files, but that may be boring for you. O: http://qa.debian.org/popcon-png.php?packages=dovecot-common%20courier-base&show_installed=on&want_legend=on > For your planning, I hope to get another batch done during December, so > depending on your next targetted upload I don't know, there has not been a lot of changes recently, but Nicolas added a feature this summer (in order to translate control files), and I would love to see the po4a package in the Debian archive in order to provide a patch for debtags to include tags descriptions. Some translations are already available on package.d.o, my wish would be, once include in debtags, to offer the translated tags descriptions in various front-ends like aptitude… Sadly, I haven't prepared any debtag patch yet to include those translations, but when I'll find some time to do so, I'll ask for a revision release of po4a (if the German translation is not complete then, we'll upload another revision before or during the freeze to make it complete anyway). Nicolas, in case you've read so far, could you please remind me the needed commands to generate the PO and control files for debsums from the packages.d.o PO files (just in case you still have them handy, I'll reproduce something if I've been silly enough not to save my history). Anyway, we'll send a mail to translators with incomplete translation at least ten days before the next release. > [1] I got an e-mail with […] > The reason it is being held: > > Message body is too big: 99476 bytes with a limit of 40 KB Well, it's quite self explained: too big messages don't go to the commit list. I don't think it's really an issue: too big changes are generally update translations (so it should not really need any review from the po4a developers, given that such review would already have happen in a translation coordination mailing list, and that po4a developers might not be qualified in $language anyway ;-), or PO and POT update after some massive change, so a call for translation will follow anyway. Regards David
signature.asc
Description: OpenPGP digital signature
