Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Thu, 24 Mar 2005 08:36:25 -0800, "Josh Skains" <JSkains at deltad.com> wrote: >This all gets more entertaining. In version 2.0.51d, the one that is >supposed to still work for scripts is broke on STDIN. The files aren't >passed at all. Which script are you referring to? I know that many people use CVSMailer on 2.0.51d and it uses the notify, taginfo and loginfo scripts. If there was a break in any of these I would have gotten word of it long ago. For what I know this version handles these scripts OK. > >Is CVSNT stable enough for production? It seems like it isn't getting >tested at all. What constitutes a "stable" release when the stable >releases have so much broken? Depends on what you mean by "so much broken"... I think that Tony's focus is on the cvs functionality rather than on the scripting. So he actually runs quite substantial tset suites against a test release before it is published. Then a rather long time of stabilization is spent with feedback from cutting edge users after a candidate for release has been made. Only thereafter will a release be made. Most of what CVSNT does in recent releases compared to say 2.0.41 is feature adding. The basic stuff is the same as always. So what is breaking is probably stuff that is not even in the GNU CVS. > >BTW, that spacing issue on the output isn't a script issue. CVSNT >inserts blank lines in-between each line. This doesn't happen on the >standard cvs. I don't know what this is, really... (spacing???) > I am sorry to say that the branch tag removal from the loginfo STDIN passed me by during the many tests prior to 2.5.01 release, but it is a thing that does not matter for the versioning system, just for some emails... /Bo (Bo Berglund, developer in Sweden)