OK thanks. I've done a bunch of work on the build scripts and am almost
ready to send the updates to [EMAIL PROTECTED]
What format should I send them in? The easiest I could think would be to
ZIP them up and send them as an attachment, but if preferred I could send
DIFFs (although some of the files have CR/LF issues that make DIFF's output
look rather ugly).
How do I go about getting an account for the RT database?
Thanks for your help, I look forward to contributing.
Sincerely,
Ken
PS Short list of fixes: moved a bunch of the "setup" from the README-NT file
into the build (copying files); added some sanity-checking in the
ntbuild.bat script; put "if exist" in front of all DEL commands; fixed the
"clean" target (couldn't do two "clean"s in a row, as it deleted the
src\config\NTMakefile.version file which is included in many NTMakefiles);
and am submitting my chkbuild.pl script which can be used to check for
errors that (for some reason or other) nmake doesn't stop on.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Derrick J Brashear
Sent: Saturday, February 15, 2003 2:09 PM
To: [EMAIL PROTECTED]
Subject: RE: [OpenAFS-devel] OpenAFS 1-2.9-rc2 build with W2k, Visual
Studio.net7, Oct 2002 SDK
On Fri, 14 Feb 2003, Ken Beal wrote:
> > (how did [EMAIL PROTECTED] end up getting cc'd on this?)
>
> My mistake, I hit Ctrl+Shift+R instead of Ctrl+R (because Ctrl+R was going
> *only* to openafs-devel-admin (brain-dead Outlook)), and forgot to remove
> the admin.
Ok, at least I know now which mail client is guilty ;-)
> Question: where should I submit fixes to the build scripts?
[EMAIL PROTECTED]
There's an RT database (Request Tracker) behind it. There's a link on the
left side of www.openafs.org.
> Is there a BugZilla for OpenAFS? Or if not BugZilla, a database/list of
> some sort documenting AFS bugs? I've heard there are some memory leaks in
> Windows and I'd like to try finding and fixing them, but I need more info.
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-devel
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-devel
