[2116] in Kerberos_V5_Development
[Theodore Y. Ts'o: Re: Any objections to checking in files on mainline branch?]
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Tue Dec 17 15:05:47 1996
Date: Tue, 17 Dec 1996 15:05:12 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: krbdev@MIT.EDU
FYI, for everyone who might be making changes to the MIT CVS tree,
here's the explicit word about changes to the mainline... (nothing
earth-shattering, but I thought I should just make the announcement
officially.)
- Ted
------- Forwarded Message
Date: Tue, 17 Dec 1996 11:45:18 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Ezra Peisach <epeisach@MIT.EDU>
In-Reply-To: Ezra Peisach's message of Mon, 16 Dec 1996 20:37:49 EST,
<9612170137.AA13368@kangaroo.mit.edu>
Subject: Re: Any objections to checking in files on mainline branch?
Address: 1 Amherst St., Cambridge, MA 02139
Phone: (617) 253-8091
Date: Mon, 16 Dec 1996 20:37:49 EST
From: Ezra Peisach <epeisach@MIT.EDU>
nI've been fixing up some warnings in the krb5 code. (like using int
vs. krb5_boolean). Can I check them into the mainline files - or do
you want to keep the CVS tree untouched?
Go ahead and check stuff into the mainline src directory. (doc/ hasn't
been merged yet). For anything that you think is worthy of putting into
patch against 1.0, (I'm thinking that we'll have a patchlevel 1 very
shortly), check it in as a separate commit from the rest, and in the
gnats PR entry, make a note of what the relevant files that were changed
and what their revision numbers were. That'll make it easier for us to
propagate the changes back to the V1_0_BRANCH when we make the
patchlevel release....
Thanks!!
- Ted
------- End Forwarded Message
