Subversion commit notifications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've asked sunsite for a list to receive subversion commit notifications, mainly so we keep our lists on the same site. I haven't had a heckuvalot of luck in getting responses from them, so far, and I'd really like to have the list set up right away, so in the meantime, I've set it up at http://addictivecode.org/mailman/listinfo/wget-notify/ . This will receive all commit notifications, and is intended for devs to be aware of what everyone is working on. I'm thinking about having changes that just hit the trunk or the release branches (that is, everything but in-progress work in the bug branches) automatically post to wget-patches, if that seems like a good idea. That way devs won't have to post to wget-patches when they make a fix, it'll just be there, and the only manual posting that will need to happen is patch submission. - -- 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 iD8DBQFGjy3r7M8hyUobTrERCFWZAKCGUq/5NVPRaAdHYF9IkV0fhnMt6wCfQKom HWXIi9DkKyrF9cAieZUzw08= =07CB -END PGP SIGNATURE-
Re: Subversion commit notifications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Micah Cowan wrote: This will receive all commit notifications, and is intended for devs to be aware of what everyone is working on. I'm thinking about having changes that just hit the trunk or the release branches (that is, everything but in-progress work in the bug branches) automatically post to wget-patches, if that seems like a good idea. That way devs won't have to post to wget-patches when they make a fix, it'll just be there, and the only manual posting that will need to happen is patch submission. I forgot to mention that the wget-notify list is writable, as it's also intended to permit discussion of development as it is happening. - -- 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 iD8DBQFGjy9g7M8hyUobTrERCKhjAJ9QyDbCuZUSBITcHygorZFkL5h6rwCgkA48 jZmhgWDCKRX7cXHilaHmJ4k= =nTGA -END PGP SIGNATURE-
wget on gnu.org: error on Development page
On http://www.gnu.org/software/wget/wgetdev.html, step 1 of the summary is: 1. Change to the topmost GNU Wget directory: % cd wget But you need to cd to either wget/trunk or the appropriate version subdirectory of wget/branches.
Re: wget on gnu.org: error on Development page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Tony Lewis wrote: On http://www.gnu.org/software/wget/wgetdev.html, step 1 of the summary is: 1. Change to the topmost GNU Wget directory: % cd wget But you need to cd to either wget/trunk or the appropriate version subdirectory of wget/branches. Actually, the wget directory is the trunk in that example, since it was checked out with $ svn co svn://addictivecode.org/wget/trunk wget But thank you for checking that page over for problems; let me know if you find anything else. - -- 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 iD8DBQFGj9jR7M8hyUobTrERCJoFAJ9py4pjBqDRMimQr82xpW8Bxfx3DQCggGfH AIzZTFL8r7vLVULww84beSI= =OPyZ -END PGP SIGNATURE-
Re: Subversion commit notifications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Daniel Stenberg wrote: On Fri, 6 Jul 2007, Micah Cowan wrote: I forgot to mention that the wget-notify list is writable, as it's also intended to permit discussion of development as it is happening. So the svn notify list is effectively turning into a devel list? Well, the idea for dev discussion on wget-notify is specifically to discuss changes that are actively being worked on (mainly, comments on committed code). I believe this list will still the primary dev discussion list (among other roles :) ). - -- 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 iD8DBQFGj+jN7M8hyUobTrERCOmEAJ9dWabfO7rCJzqmuuhz68v6V/V3UwCfZvto eryw3jUIFPRNr4ygYerJKx8= =9H+7 -END PGP SIGNATURE-
Re: wget on gnu.org: Report a Bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Tony Lewis wrote: The “Report a Bug” section of http://www.gnu.org/software/wget/ should encourage submitters to send as much relevant information as possible including wget version, operating system, and command line. The submitter should also either send or at least save a copy of the --debug output. This information is currently in the bug submitting form at Savannah: https://savannah.gnu.org/bugs/?func=additemgroup=wget But should probably be duplicated at the website as well... let me know if the current text could use improvement. Perhaps we need a --bug option for the command line that runs the command and saves important information in a file that can be submitted along with the bug report. The saved information would have to be sanitized to remove things like user IDs and passwords but could include things like the wget version, command line options, and what the command tried to do. I think perhaps such things as the wget version and operating system ought to be emitted by default anyway (except when -q is given). Other than that, what kinds of things would --bug provide above and beyond --debug? - -- 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 iD8DBQFGj+hk7M8hyUobTrERCHqtAJ9HTIFd3hOJ2R9aQBUqCtsvW2xJ1wCePOfo 67Olfti9HtI+1pYkNiCj7rc= =/Rhd -END PGP SIGNATURE-
Re: wget on gnu.org: error on Development page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Tony Lewis wrote: Micah Cowen wrote: Actually, the wget directory is the trunk in that example, since it was checked out with $ svn co svn://addictivecode.org/wget/trunk wget Checking out the code using trunk is only one of three examples. I used the third example, checking out the entire source code repository. (Don't ask me why I thought I might need it.) If it had read: Change to the topmost GNU Wget directory in the branch you want to build; for example: % cd wget then I wouldn't have submitted the comment. I suspect most people who get to the point of checking out code can figure it out, but... Fair point. I'll adjust accordingly. - -- 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 iD8DBQFGkAVK7M8hyUobTrERCP6YAJ9d6ABIftbxV8TnZk5Q/Yu5z/RqjwCfS/3q 4Z9yOMUmvJPiBg0wUtqmurE= =uNVz -END PGP SIGNATURE-
RE: wget on gnu.org: Report a Bug
Micah Cowan wrote: This information is currently in the bug submitting form at Savannah: That looks good. I think perhaps such things as the wget version and operating system ought to be emitted by default anyway (except when -q is given). I'm not convinced that wget should ordinarily emit the operating system. It's really only useful to someone other than the person running the command. Other than that, what kinds of things would --bug provide above and beyond --debug? It should echo the command line and the contents of .wgetrc to the bug output, which even the --debug option does not do. Perhaps we will think of other things to include in the output if this option gets added. However, the big difference would be where the output was directed. When invoked as: wget ... --bug bug_report all interesting (but sanitized) information would be written to the file bug_report whether or not the command included --debug, which would also direct the debugging output to STDOUT. The main reason I had for suggesting this option is that it would be easy to tell newbies with problems to run the exact same command with --bug bug_report and send the file bug_report to the list (or to whomever is working on the problem). The user wouldn't see the command behave any differently, but we'd have the information we need to investigate the report. It might even be that most of us would choose to run with --bug most of the time relying on the normal wget output except when something appears to have gone wrong and then checking the file when it does. Tony
Re: wget on gnu.org: error on Development page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Micah Cowan wrote: Tony Lewis wrote: Micah Cowen wrote: Actually, the wget directory is the trunk in that example, since it was checked out with $ svn co svn://addictivecode.org/wget/trunk wget Checking out the code using trunk is only one of three examples. I used the third example, checking out the entire source code repository. (Don't ask me why I thought I might need it.) If it had read: Change to the topmost GNU Wget directory in the branch you want to build; for example: % cd wget then I wouldn't have submitted the comment. I suspect most people who get to the point of checking out code can figure it out, but... Fair point. I'll adjust accordingly. Done. Lemme know if that works for you. - -- 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 iD8DBQFGkDe87M8hyUobTrERCJ6vAJwK3UVnVmmpKzjkeEwPBYBumowygwCgiic9 aXIZ8upGU7Ru1fnJlmjoKqU= =ep82 -END PGP SIGNATURE-
Re: wget on gnu.org: Report a Bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Micah Cowan wrote: Tony Lewis wrote: The “Report a Bug” section of http://www.gnu.org/software/wget/ should encourage submitters to send as much relevant information as possible including wget version, operating system, and command line. The submitter should also either send or at least save a copy of the --debug output. This information is currently in the bug submitting form at Savannah: https://savannah.gnu.org/bugs/?func=additemgroup=wget But should probably be duplicated at the website as well... let me know if the current text could use improvement. I've copied the text to the website, along with a link to Simon Tatham's essay on reporting bugs. I also added a small section regarding the IRC #wget channel on FreeNode. - -- 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 iD8DBQFGkDhh7M8hyUobTrERCDBQAJ4ln3eWsbdbsa5ahfB7kv5tHIc1wACeLSIj uXkezPuzt7GMoiXvUemMT9U= =2dVK -END PGP SIGNATURE-
Bug update notifications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The wget-notify mailing list (http://addictivecode.org/mailman/listinfo/wget-notify) will now also be receiving notifications of bug updates from GNU Savannah, in addition to subversion commits. - -- 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 iD8DBQFGkG0Q7M8hyUobTrERCLVXAJwP7ru9v88PFF6PgREWTn0XF7XRnwCfY1hd 4W1KLuYYRvZ0pSXOLk6YY/Y= =TOP4 -END PGP SIGNATURE-
RE: wget on gnu.org: error on Development page
Micah Cowan wrote: Done. Lemme know if that works for you. Looks good
