-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rafael Anschau wrote:
bash-3.2$ wget http://www.intel.com/design/processor/manuals/253667.pdf
--20:01:01-- http://www.intel.com/design/processor/manuals/253667.pdf
= `253667.pdf'
Resolving www.intel.com... 81.52.134.16, 81.52.134.24
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Esin,
Unfortunately, the patch you've provided really doesn't seem
appropriate, as it would try to convert an enumeration value into a
pointer, which, while it might shut up a warning on your compiler, has a
much higher chance of breaking than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sorry, hadn't noticed this was also sent to the list. Sending a copy there.
Christopher G. Lewis wrote:
Micah -
Your latest checkin for Spider.C breaks the windows build:
snip
logprintf (LOG_NOTQUIET, ngettext(Found %d broken link.\n\n,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gisle Vanem wrote:
I've been porting Wget to MSDOS using the djgpp environment.
The task was rather simple; adding a new directory ./msdos with
a config.h and Makefile.dj. I intend to support other DOS-compilers
later.
Please take a look at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jason Mancini wrote:
Since I don't know why that code exists, here is a patch that should
fix the issue, and remain compatible with whatever the heck that
decrementing code tries to achieve on some system I have probably
never seen:
Thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi folks,
Development for Wget has been proceeding about as planned, which is
pretty amazing considering that the few core developers we have are all
busy with their own day jobs. We are very nearly ready to release Wget
version 1.11, and are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeff Holicky wrote:
I am trying to download a page from a specific site.
The page URL is: http://stockcharts.com/charts/adjusthist.html
First, when you open a browser, say FireFox and go to the site - the top
part (above the dotted line)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've just merged a bunch of things into the current trunk, including
Mauro's latest changes related to when HEAD is sent (concerning which he
recently sent an email). Please feel free to beat on it, and report any
bugs here!
- --
Micah J. Cowan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Goul_duKat wrote:
blanked some info with xxx
file used
http://files.filefront.com/Oulton_ParkBumpFixrar/;6524403;;/fileinfo.html
is possible to fix this wrong behavior so instead to try to use the url
to build the filename use the right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A bug was submitted to Ubuntu's Malone bugtracker, complaining that
- --background shoud not create a wget-log file when --quiet has been
specified:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/135063
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
I did only a few first tests now, because the basic test already had a
problem:
With default options the local timestamps are not set at all.
Options: no spider, no -O, no content-disposition:
no timestamping, no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andreas Kohlbach wrote:
Hi,
though the man page of wget mentions .netrc, I assume this is a bug.
For my understanding if you provide a --user=user and --password=password
at the command line this should overwrite any setting elsewhere, as in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ed wrote:
Seen this twice now but unable to track down how it happens.
I am crawling a list of websites which are being kept in a cache area.
snip
A small number of files end up in the wrong location, evidence from
the logs indicates that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
As Josh points out, the question remains whether this should be our
behavior; I vote yes, as command-line arguments should always override
rc files, in general. Of course, these values
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andreas Kohlbach wrote:
On Tue, Sep 04, 2007 at 02:48:25PM -0700, Micah Cowan wrote:
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
As Josh points out, the question remains whether this should be our
behavior; I vote yes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Aram Wool wrote:
Hi, I'm having trouble retrieving an mp3 file from a url of the form
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Jochen Roderburg [EMAIL PROTECTED]:
So it looks now to me, that the new error (local timestamp not set to remote)
only occurs in the cases when no HEAD is used.
This (new) piece of code in http.c (line 2666
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Thomas wrote:
command.com
By the way, Josh and your messages are being put out to the list in
dupicates (at least, that`s what I`m seeing on my end).
Not really; we've been Cc'ing you. I don't think we knew whether you
were subscribed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Thomas wrote:
Please ignore. It was needing the \\, like Josh said.
Out of curiosity, what command interpreter were you using? Was this
command.com, or something else like rxvt/Cygwin?
- --
Micah J. Cowan
Programmer, musician, typesetting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Thomas wrote:
I know this is probably something simple I screwed up, but the
following commands in a Windows batch file return the error Bad command
or file name for the wget command
It sounds to me like you don't have wget in your PATH.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Thomas wrote:
Is there a way to use wget to get file from links that result
from Active Server Pages (ASPs) on a web page? For example, to get the
files in the links on the page returned by the URL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The main informational site for GNU Wget is now at
http://wget.addictivecode.com/; the Wget Wgiki.
--
The original motivation for starting a wiki for Wget was that I needed a
forum for collaboration on specifications and design for future
Josh Williams wrote:
On 9/7/07, Micah Cowan [EMAIL PROTECTED] wrote:
Doh! Of course, it's .org. Fortunately all the other links, including
the ones from the site at gnu.org, seem to be correct.
Unfortunately for you, your typo is now an official piece of free
software history! :D
Just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
Zitat von Jochen Roderburg [EMAIL PROTECTED]:
So it looks now to me, that the new error (local timestamp not set to
remote)
only occurs in the cases when no HEAD is used
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Senthil Kumaran S wrote:
On 9/7/07, Micah Cowan [EMAIL PROTECTED] wrote:
The main informational site for GNU Wget is now at
http://wget.addictivecode.com/; the Wget Wgiki.
Is it http://wget.addictivecode.com/ or http://wget.addictivecode.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
Hm... that change came from the Content-Disposition fixes. I'll investigate.
OK, but I hope I am still allowed to help a little with the investigation ;-)
Oh, I'm always very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I haven't discovered why yet, but all of addictivecode.org's internet
services went down last night around 7:30 pm PDT (02:30 UTC). The web
and ssh services were brought back up in response to an email query,
around 2:30 am PDT (09:30 UTC), but it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
I haven't discovered why yet, but all of addictivecode.org's internet
services went down last night around 7:30 pm PDT (02:30 UTC).
Note that the addictivecode.org failure was completely unrelated to the
main Wget mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hex Star wrote:
Oh and the configuration on which wget was running is: PowerBook G4
1.5ghz (PowerPC), 768mb ram, Mac OS X 10.4.10
One crucial bit of information you've left out, is which version of Wget
you're running. :)
Sorry if it took a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alex Owen wrote:
Hello,
If i run :
wget http://server.domain/file
How can I differentiate between a network problem that made wget fail
of the server sending back a HTTP 404 error?
( I have a use case described in debian bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Todd Plessel wrote:
Q1. Is there a way that I can run wget that somehow avoids this
timeout. For example, by sending an out-of-band ack to stderr every
30 seconds so httpd does not disconnect.
By out-of-band, I mean it cannot be included in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Todd Plessel wrote:
Q2. If not, then could the PERL-CGI script be modified to spawn a
thread that writes an ack to stderr to keep the httpd from timing-out?
If so, can you point me to some sample code?
This would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Josh Williams wrote:
On 9/12/07, Erik Bolstad [EMAIL PROTECTED] wrote:
Hi!
I'm doing a master thesis on online news at the University of Oslo,
and need a software that can download html pages based on RSS feeds.
I suspect that Wget could be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
I see also a conflict between older changes by Mauro
and the latest changes by Micah in this area.
Actually, I never made any changes to this area that I recall; just
merged in changes others made. :)
I'm not really sure
Hrvoje Niksic wrote:
Subject:
Re: Wget Bug: recursive get from ftp with a port in the url fails
From:
baalchina [EMAIL PROTECTED]
Date:
Mon, 17 Sep 2007 19:56:20 +0800
To:
[EMAIL PROTECTED]
To:
[EMAIL PROTECTED]
Message-ID:
[EMAIL PROTECTED]
MIME-Version:
1.0
Content-Type:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Aram Wool wrote:
hi, I'm using wget with this url:
http://www.twis.org/audio/podpress_trac/web/147/0/TWIS_2007_09_11.mp3
the directory named 147 increases by 1 each week, corresponding to an mp3
with a new date. I can use macros to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[EMAIL PROTECTED] wrote:
Not sure if it's a bug, but NTLM authentication has just started to fail
connecting to SharePoint running IIS, after it's been working for
years. The URL is accessible using IE or Mozilla using the same login
for the quick response. I looked on the FAQ and didn't see
anything relevant. I installed the latest code, but I still get the
same error. Any other suggestions???
-Original Message-
From: Micah Cowan [mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Not sure if it's a bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since I do virtually all my work on a laptop, which is usually but not
always connected to the Wired, I have begun experimenting with
distributed SCMs. I have recently been using Mercurial for work on Wget,
and then synching the work with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matthew Woehlke wrote:
Micah Cowan wrote:
Since I do virtually all my work on a laptop, which is usually but not
always connected to the Wired, I have begun experimenting with
distributed SCMs. I have recently been using Mercurial for work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The subversion repository (including trunk, tags, branches) takes up 27MB.
A working copy checked out from Subversion (just trunk) occupies about
12MB; about 5.1MB are the working files, about 6.2MB are .svn/
directories and their contents (that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
(Whoops, of course I meant to send this to the list, rather than to Tony
alone. Resent. Sorry Tony!)
Tony Lewis wrote:
Micah Cowan wrote:
As I see it, the biggest concern over using git would be multiplatform
support. AFAICT, git has a great
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
(Not Cc'ing Gerard, as I'm not sure he wants to be included in this
tangent.)
Tony Lewis wrote:
Unfortunately, at least as far as I can tell, wget does not issue an
exit code if it has downloaded a newer file.
Better exit codes is on the wish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Stephen Schachter wrote:
With some innocence, I tried changing weblogic server parameters, increasing
the number of threads, and the percentage of threads used to process
requestst, but this dod no good. With four concurrent requesters
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
www.mail wrote:
wget -nc http://www.google.com/;
the index.html file is downloaded as expected. However, running the
same command again causes wget to crash. The wget output is:
Confirmed, on GNU/Linux. Thanks for the report.
There seems to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
www.mail wrote:
wget -nc http://www.google.com/;
the index.html file is downloaded as expected. However, running the
same command again causes wget to crash. The wget output is:
Confirmed, on GNU/Linux. Thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
And now, for a change, a case, that works now (better) ;-)
This is an example where a HEAD request gets a 500 Error response.
Wget default options again, but contentdisposition=yes to force a HEAD.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steven M. Schweda wrote:
From: Micah Cowan
- tms = time_str (NULL);
+ tms = datetime_str (NULL);
Does anyone think there's any general usefulness for this sort of
thing?
I don't care much, but it seems like a fairly harmless
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steven M. Schweda wrote:
But, since any specific transaction is unlikely to take such a long
time, the spread of the run is easily deduced by the start and end
times, and, in the unlikely event of multiple days, counting time
regressions.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
There is little left to finish up for Wget 1.11. I've decided to leave
certain issues related to Content-Disposition until 1.12
(Content-Disposition support in Wget 1.11 will be considered
experimental). The few other remaining issues are awaiting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Wright wrote:
My usage is counter to your assumptions below.[...]
A change as proposed here is very simple, but
would be VERY useful.
Okay. Guess I'm sold, then. :D
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
The problem you pointed out that causes the failure to properly
timestamp when HEADs aren't issued seems, to my reading, to be simply
regressable for the fix. Mauro's fixes don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
Jochen Roderburg wrote:
Yes, this one is still open, and the other one that wget -c always starts
at 0
again.
Do you mean the (local 0) thing? That should have been fixed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Josh Williams wrote:
On 10/4/07, Brian Keck [EMAIL PROTECTED] wrote:
I would have sent a fix too, but after finding my way through http.c
retr.c I got lost in url.c.
You and me both. A lot of the code needs re-written.. there's a lot of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Thomas wrote:
Idea for future wget versions: It would be nice if I could
invoke wget programmatically and have options like returning data in
buffers versus files (so data can be searched and/or manipulated in
memory),
This can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Keck wrote:
Hello,
I'm wondering if I've found a bug in the excellent wget.
I'm not asking for help, because it turned out not to be the reason
one of my scripts was failing.
The possible bug is in the derivation of the filename from
Reynir (Cc'd) writes:
Wget 1.10.2 on a Windows98 box will occasionally time out resolving a
host (I've set all time-outs to 45s, being stuck with a modem) and
hang. The -d switch adds nothing useful.
and has also reproduced this on 1.11.
Is it possible there are issues with TerminateThread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Yes, this one is still open, and the other one that wget -c always starts
at 0
again.
Do you mean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Unfortunately, however, a new regression crept in:
In the case timestamping=on, content-disposition=off, no local file present it
does now no HEAD (correctly), but two (!!) GETS and transfers the file two
times.
Ha!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ralf Wildenhues wrote:
Hello Micah,
* Micah Cowan wrote on Sat, Oct 06, 2007 at 12:04:53AM CEST:
Ralf Wildenhues wrote:
Remove all files that will be installed/governed by automake:
(We keep deprecated mkinstalldirs for now, as po
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A. P. Godshall wrote:
Hi
New to the list.
Welcome!
Wrote a patch that Works For Me to limit to a percent of measured
bandwidth. This is useful, like --limit-rate, in cases where an
upstream switch is poorly made and interactive users get
And here's another post that apparently got sent with an erroneous
signature. I think I may have figured out what was wrong; I specifically
remember that I was still holding shift down when I typed one of the
spaces in my passphrase... maybe that results in some screwiness...
--
Micah J. Cowan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Jochen Roderburg wrote:
Unfortunately, however, a new regression crept in:
In the case timestamping=on, content-disposition=off, no local file present
it
does now no HEAD (correctly), but two (!!) GETS and transfers the file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Several items to announce.
One, the Mercurial trunk repository has been renamed to mainline,
which seems a better label, considering that we're not really talking
about a trunk and branches any more (in fact, the mainline repo
could conceivably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Three, I have CLOSED THE TRUNK in subversion (svn rm $WGETROOT/trunk).
Changes to wget-1.11 will continue to be merged to
$WGETROOT/branches/1.11 until the release, after which point Subversion
will no longer be used
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ray Phillips wrote:
I thought I'd report my experiences trying to install wget 1.10.2 on
NetBSD/i386 3.1. I'll append the contents of config.log to the end of
this email.
snip
gcc -I. -I. -DHAVE_CONFIG_H
].
Currently maintained by Micah Cowan [EMAIL PROTECTED].
$ wget --version # from a tarball, no repo
GNU Wget 1.12-devel
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
...
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Wright wrote:
I think there is still a case for attempting percent limiting. I agree
with your point that we can not discover the full bandwidth of the
link and adjust to that. The approach discovers the current available
bandwidth and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
(We don't have reply-to's set; I've re-included the list on this.)
Ray Phillips wrote:
Thanks for your reply Micah.
Ray Phillips wrote:
I thought I'd report my experiences trying to install wget 1.10.2 on
NetBSD/i386 3.1. I'll append the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Jim Wright [EMAIL PROTECTED] writes:
I think there is still a case for attempting percent limiting. I
agree with your point that we can not discover the full bandwidth of
the link and adjust to that. The approach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel Stenberg wrote:
On Wed, 10 Oct 2007, Micah Cowan wrote:
It appears from your description that Wget's check in http-ntlm.c:
#if OPENSSL_VERSION_NUMBER 0x00907001L
is wrong. Your copy of openssl seems to be issuing a number lower than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
The scenario I was picturing was where you'd want to make sure some
bandwidth was left available so that unfair routers wouldn't screw
your net-neighbors. I really don't see this as an attempt to be
unobtrusive at all.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ray Phillips wrote:
Ray, if you add the line
#include openssl/opensslv.h
along with the other openssl #includes, does it fix your problem wrt
openssl-9.7d?
I made this change:
% diff -u http-ntlm.c.orig http-ntlm.c
--- http-ntlm.c.orig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thomas Wolff wrote:
Hi,
as requested, I am sending you the output of configure and config.log
for checking the problem that my compiled wget does not retrieve
over https (Unsupported scheme).
Thomas, I don't see that anything went wrong at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
On 10/10/07, Micah Cowan [EMAIL PROTECTED] wrote:
My current impression is that this is a useful addition for some limited
scenarios, but not particularly more useful than --limit-rate already
is. That's part of what makes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
On 10/11/07, Micah Cowan [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
On 10/10/07, Micah Cowan [EMAIL PROTECTED] wrote:
My current impression is that this is a useful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
...
I have, yes. And yes, it's a very small patch. The issue isn't so much
about the extra code or code maintenance; it's more about extra
documentation, and avoiding too much clutter of documentation and lists
of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Wright wrote:
On Thu, 11 Oct 2007, Micah Cowan wrote:
It's not really about this option, it's about a class of options. I'm in
the unenviable position of having to determine whether small patches
that add options are sufficiently useful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thomas Wolff wrote:
So I think it's clear the version thus produced was invoked.
Yeah, guess it couldn't be that easy! :)
Hm... well, can you verify that src/config.h has been correctly
generated to #define HAVE_SSL? If you go to src/ and type rm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
Among other things, version.c is now generated rather than
parsed. Every time make all is run, which also means that make
all will always relink the wget binary, even if there haven't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Godshall wrote:
[Jim]
Well, we need the plugin architecture anyway. There are some planned
features (JavaScript and MetaLink support being the main ones) that have
no business in Wget proper, as far as I'm concerned, but are inarguably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
FYI, I've removed the PATCHES file. Not because I don't think it's
useful, but because the information needed updating (now that we're
using Mercurial rather than Subversion), I expect it to be updated again
from time to time, and the Wgiki seems to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
Among other things, version.c is now generated rather than
parsed. Every time make all is run, which also means that make
all will always relink the wget binary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
FYI, I've removed the PATCHES file. Not because I don't think it's
useful, but because the information needed updating (now that we're
using Mercurial rather than Subversion), I expect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/13/07, Tony Godshall [EMAIL PROTECTED] wrote:
OK, so let's go back to basics for a moment.
wget's default behavior is to use all available bandwidth.
Is this the right thing to do?
Or is it better to back off a little after a bit?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joshua Szanto wrote:
http://www.hlrse.net/Qwerty/wget_glitch.gif
I have no idea how that happened. My theory is this...
I start downloading files.tar as normal, it starts at 0 and counts up to
~2.5GB (so far this is true). (Here's the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
It's hard to be confident I'm not introducing more issues, with the
state of http.c being what it is. So please beat on it! :)
This time it survived the beating ;-)
Yay
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andreas Pettersson wrote:
Andreas Pettersson wrote:
Have there been any progress with this patch since this post?
http://www.mail-archive.com/wget@sunsite.dk/msg09502.html
*bump*
Anyone knows the status of this?
Not yet installed... don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher G. Lewis wrote:
OK, so I'm trying to be open minded and deal with yet another version
control system.
I've cloned the repository and built my mainline. I do not
autogenerate a version.c file in windows. Build fails missing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mainline now has replaced a few of Wget's portability pieces with
corresponding gnulib modules. This has resulted in significant changes
to what needs to be built where, so non-Unix builds are probably further
broken (...sorry, Chris, Gisle...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Just getting a chance to look a bit more closely at this again.
Christian Roche wrote:
Hi there,
please find attached two small patches that could be
considered for wget (against revision 2276).
patch-utils changes the file renaming
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Okay, now that it's decided this thing will go in...
I'm kinda leaning toward the idea that we change the parser for
- --limit-rate to something that takes a percentage, instead of adding a
new option. While it probably means a little extra coding,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
Make my src changes, create a changeset... And then I'm lost...
Alright, so you can make your changes, and issue an hg diff, and
you've basically got what you used to do with svn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matthias Vill wrote:
I would appreciate having a --limit-rate N% option.
So now about those broken cases. You could do some least of both
policy (which would of course still need the time to do measuring and
can cut only afterwards).
Or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Josh Williams wrote:
On 10/15/07, patrick robinson [EMAIL PROTECTED] wrote:
Hello,
I want to unsubscripe from this list but lost my registration e-mail.
How is this performed?
I haven't seen this original message yet.
You can find this (and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Josh Williams wrote:
On 10/15/07, Micah Cowan [EMAIL PROTECTED] wrote:
Note that this doesn't help him much if he's lost his registration e-mail.
Patrick, you'll probably have to go bug the staff at www.dotsrc.org, who
hosts this list; send
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've improved the generation of version.c, removing the intermediate
generation of an hg-id file and using a more portable replacement for
hg id | cut -d ' ' -f 1 (can be used on Windows and MS-DOS).
The relevant lines in src/Makefile.am are now:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
version.c: $(wget_SOURCES) $(LDADD)
printf '%s' 'const char *version_string = @VERSION@' $@
-hg log -r tip --template=' ({node|short})' $@
printf '%s\n
Micah Cowan wrote:
I've improved the generation of version.c, removing the intermediate
generation of an hg-id file and using a more portable replacement for
hg id | cut -d ' ' -f 1 (can be used on Windows and MS-DOS).
The relevant lines in src/Makefile.am are now:
version.c
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
I may take liberties with the Make environment, and assume the
presence of a GNU toolset, though I'll try to avoid that where it's
possible.
Requiring the GNU toolset puts a large burden on the users of non-GNU
systems (both free
101 - 200 of 506 matches
Mail list logo
