wget.texi translations?

Hello, I got a translated wget.1 manpage into russian. I think translations should go into the upstream releases so everybody profits from this. The question is now how should the translator submit such a translation? The .po translations are done by http://translationproject.org/domain/wget.html

Re: wget.texi translations?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Noèl Köthe wrote: Hello, I got a translated wget.1 manpage into russian. I think translations should go into the upstream releases so everybody profits from this. The question is now how should the translator submit such a translation? The

Responses to wget-notify will be directed to wget@sunsite.dk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, Effective immediately, messages sent to wget-notify will have the Reply-To header set to wget@sunsite.dk. I am abandoning the earlier idea of combining commit notifications with discussion threads _on_ those notifications. I still want to

[Fwd: Bug#281201: wget prints it's progress even when background]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following bug was submitted to Debian's bug tracker. I'm curious what people think about this suggestion. Don't we already check for something like redirected output (and force the progress indicator to dots)? It seems to me that if that is

[Fwd: Re: [Req #20202] wget-patches, non-subscriber authentication]

The Dotsrc.org staff have enabled the same confirmation process for wget-patches as had been in place for wget; hopefully we'll see less spam, so the patches will stand out more clearly. :) -Micah Original Message Subject: Re: [Req #20202] wget-patches, non-subscriber

1.11 Release Date: 15 Sept

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've been keeping a schedule to organize what needs to get done and when I expect things to be done by. It's been a rough schedule; however, I believe it's complete enough to reveal now, along with an announcement regarding the expected release date