[cvsnt] Re: loginfo is "broken" in build 62

Terris Linenbach terris at terris.com
Thu Dec 19 07:00:31 GMT 2002

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.

My point was that existing scripts are broken, except for yours and any
other script that was written specifically to handle cvsnt build 62 and
later.  If such a change was made to loginfo, which surely more people use
compared taginfo, there will be a lot of sore toes.

"Bo Berglund" <bo.berglund at telia.com> wrote in message
news:52q20v82ic5gdiia0vllfrp5sf4pt8c1ut at 4ax.com...
> On Wed, 18 Dec 2002 22:20:02 -0800, "Terris Linenbach"
> <terris at terris.com> wrote:
> >
> >PS, Tony, can you fix loginfo the way you fixed taginfo, i.e., pass all
> >via STDIN rather than via the command line?  I realize this would break
> >existing scripts so would it be possible to either differentiate in the
> >"loginfo" file or create a new "loginfo2" file?  I dunno, I think
> >like this should have been done for "taginfo" so as to not break existing
> >taginfo scripts as well.
> >
> I have a taginfo script handler that did not break...
> You can simply check if there are more command line values than the
> ones you put there yourself in the script call. If there are then the
> taginfo runs the old way, otherwise read the stdin data. Works fine
> for me, the same script handler operates both on new and old cvsnt
> installations.
> /Bo
> (Bo Berglund, developer in Sweden)

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook