Full_Name: Brad Rubenstein Version: 1.1.2 OS: solaris 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (208.168.16.140) A suggestion: if we put /* $Header$ */ at the top of all source files, I can easily figure out the revision number of some problem code, when I have no context except the source file (long after I've pulled a release and unzipped it, which release it is and what patchlevel, is information that I no longer have). Alternatively (and perhaps easier), when you build the tgz files for the distributions, leave the CVS directories in, so after the tgz is long gone, there is still enough information in the source code to figure out which release the sources came from.
moved from Incoming to Software
At 02:22 AM 1/13/99 GMT, brad.rubenstein@gs.com wrote: >Full_Name: Brad Rubenstein >Version: 1.1.2 >OS: solaris 2.6 >URL: ftp://ftp.openldap.org/incoming/ >Submission from: (NULL) (208.168.16.140) > > >A suggestion: if we put /* $Header$ */ at the top of all >source files, I can easily figure out the revision number of some problem code, I had problem initially with CVS variable substitute causing conflicts during merges. However, this was primarily with preexisting RCS tags from the U-Mich distribution. I may try to add new tags to a couple of a file or two, but if they cause conflicts they are gone (merges are hard enough). If they don't cause problems, then we can consider adding them across the board. >when I have no context except the source file (long after I've pulled a release >and >unzipped it, >which release it is and what patchlevel, is information that I no longer have). >Alternatively (and perhaps easier), when you >build the tgz files for the distributions, >leave the CVS directories in, so after the tgz is long gone, there is still >enough information in the source code to figure out >which release the sources came from. The CVS directories are only useful if you have CVS. If you have CVS, you should really grab OpenLDAP via AnonCVS or CVSup. And, if you applied a patch, the patch (generated using CVSweb) the files in CVS wouldn't be updated.
Kurt@OpenLDAP.org wrote: > The CVS directories are only useful if you have CVS. If you have CVS, > you should really grab OpenLDAP via AnonCVS or CVSup. And, if you applied > a patch, the patch (generated using CVSweb) the files in CVS wouldn't > be updated. I have CVS, but I'm behind a serious corporate firewall, so can't use it for openldap. However, if i know there is a bug in line 52 of search.c, I can look up the revision in CVS/Entries (if it is there), and what the tag was (in CVS/Tag). I guess I could say "there is a bug in line 52 of .../search.c in openldap-stable-981231", but I'm open to whatever you prefer. Brad
changed notes changed state Open to Suspended
moved from Software to Software Enhancements
changed notes changed state Suspended to Closed
Need to be tested with latest CVS to ensure merge conflicts do not result from change. Not needed.