Date: Tue, 9 May 1995 23:15:31 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: asami@cs.berkeley.edu (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) Cc: wollman@halloran-eldar.lcs.mit.edu, paul@isl.cf.ac.uk, bde@zeta.org.au, ache@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-gnu@freefall.cdrom.com Subject: Re: cvs commit: src/gnu/lib/libreadline Makefile Message-ID: <199505100615.XAA06868@gndrsh.aac.dev.com> In-Reply-To: <199505100607.XAA02002@silvia.HIP.Berkeley.EDU> from "Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=" at May 9, 95 11:07:17 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > * > The following events cause major version numbers to be bumped > * > > * > (1) deleting a function > * > (2) interface change (different argument order, etc.) > * (3) change of functionality in a function (ie, when I add %b to > * printf it will require a major number bump, since calling the > * old printf with a %b will just blow it out of the water). > > Um, if the %b didn't exist in the old function, this should be a minor > number change, no? Because code compiled with the old function (and > these programs presumable won't use %b) can run with the new function, > but not vice versa.... Ah, yea, your right. A minor bump would take care of the problem. I knew something had to bump, and at 8:00 am this morning after hacking all night I was not thinking very clear. We need to expand your little list to include when to bump what part. > > * > If nobody objects, then this will become the official policy. :) > * > * Please commit it as /usr/src/policy/library_versions > > Hey, I didn't propose to make a new directory under /usr/src. ;) We do need to do something like this. Probably the location above is not optimal, perhaps /usr/src/share/doc/policy. I have another contribution for it, but perhaps this is FAQ material, ``How to place code under a UCB style copyright, complete with a sample ready to edit''. > > We've gotta decide where to put these kind of things, though. Didn't > we have a committers.faq or something like that? (What was the > document that we let new cvs users read?) I basically point people to the cvs FAQ and the manual pages, then a few days of hand holding. We do have another piece of policy here though, and that is about how we use CVS, modules, no touching stuff manualy in ~ncvs, etc. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505100615.XAA06868>