-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
-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
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.
-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
-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
-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
-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.
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
-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
-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
-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,
Micah Cowan wrote:
Done. Lemme know if that works for you.
Looks good
12 matches
Mail list logo
