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 for GNU Wget 1.11. I've built in what I believe to be a fairly generous amount of flexibility. I'll add the disclaimer here, though, that when the number of active developers is roughly two, any surprises have the potential for rather large effects on the schedule. But rather than continue promises of Wget releasing Real Soon Now, I'd like to at least place a stake in the ground; and I'll do whatever I have to to meet that date. That having been said, the plan is to have 1.11 release no later than the 15th of September, with prereleases on 15 August and 1 Sept. The development schedule - which will be adjusted frequently, but whose terminal date is expected to remain constant ;) - is available at http://addictivecode.org/wget/sched-1.11.html . It was exported from Planner, a project management tool for GNOME (http://live.gnome.org/Planner); the source document is http://addictivecode.org/wget/sched-1.11.planner . The list of bugs currently targeted at 1.11 is still to be had at: https://savannah.gnu.org/bugs/index.php?go_report=Apply&group=wget&func=browse&set=custom&msort=0&report_id=189&advsrch=1&plan_release_id=101 - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlaBI7M8hyUobTrERCGJKAJ9V5RAX7RXs/XzX47hyOGrmwMUCQACfbw5L jMYC8MDV0H5MOfwE3iWxgE8= =9cXG -END PGP SIGNATURE-
[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 authentication Date: Wed, 11 Jul 2007 17:54:44 +0200 From: Claus Alboege <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Organization: Dotsrc.org - Open Source Hosting To: Micah Cowan <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> q:res Hi, Micah Cowan <[EMAIL PROTECTED]> writes: > Would it be possible to set the [EMAIL PROTECTED] mailing list to > require the same authentication from non-subscribers in order to post, > as is currently required by the wget@sunsite.dk mailing list in the same > circumstance? We're getting a bit overrun by spam. Sorry for the long delay. We have now enabled qconfirm for the wget-patches list. /Claus A Dotsrc.org Staff
[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 appropriate, then a case could be made for this as well. Perhaps instead of "shutting up", though, wget should attempt to direct to a file? Perhaps with a "one last message" to the terminal (assuming the terminal doesn't have TOSTOP set--it should ignore SIGTTOU and handle EIO to handle that case), to indicate that it's doing this. - -Micah - Original Message Subject: Bug#281201: wget prints it's progress even when background Resent-Date: Tue, 10 Jul 2007 13:57:01 +, Tue, 10 Jul 2007 13:57:02 + Resent-From: Ilya Anfimov <[EMAIL PROTECTED]> Resent-To: [EMAIL PROTECTED] Resent-CC: Noèl Köthe <[EMAIL PROTECTED]> Date: Tue, 10 Jul 2007 17:54:51 +0400 From: Ilya Anfimov <[EMAIL PROTECTED]> Reply-To: Ilya Anfimov <[EMAIL PROTECTED]>, [EMAIL PROTECTED] To: Peter Eisentraut <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] My suggestion is to stop printing verbose progress messages when the job is resumed in background. It could be checked by (successful) getpgrp() not equal to (successful) tcgetprp(1) in SIGCONT signal handler. And something like this is used in some console applications, for example, in lftp. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlThP7M8hyUobTrERCA4sAJ0RwfVIsL5UcafLkfm5qihERnRNvQCeIABc t+Y3FeNYctJsdPcPbTwYukk= =eBSi -END PGP SIGNATURE-
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 foster heavy discussion on code "as it's happening", but it's probably better for all if those discussions take place on a separate list, lest actual meaningful discussions be frequently lost in a sea of commit and bug update notifications. This activity will likely (hopefully?) increase the development-related traffic on [EMAIL PROTECTED] If it turns out to be very significant, perhaps we'll split off a list for development discussion, so we can leave wget to bugs, support and general discussion. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlSeW7M8hyUobTrERCJhrAJ4mETrS5qA1NNsQpjaL675FoO9c2QCdEiq8 bQwKQ+BVE+QSz2r2Rmdxcy4= =Ua+v -END PGP SIGNATURE-
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 .po translations are done by > http://translationproject.org/domain/wget.html but not the > manpage/wget.texi source. (This is in reference to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293596 ) I actually have no idea! I would think they would go to the translation project as well, but a google search provided zero useful hits. I'm Cc-ing the translation project coordinator, perhaps he will respond with appropriate information. However, regardless of where the manual is sent to, Nick will need to sign and send copyright disclaimer or assignment papers (something he appeared to be balking at), or I will not be able to accept them. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGlSHZ7M8hyUobTrERCDIdAJ9U0NGv6f6iySrDZnYqE2B2SV7CZACfVHU5 6wwAaMq9itLJ/X126Q36npc= =bwy6 -END PGP SIGNATURE-
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 but not the manpage/wget.texi source. thx. -- Noèl Köthe Debian GNU/Linux, www.debian.org signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
