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 Wed, 23 Mar 2005 21:27:53 -0700, Glen Starrett <grstarrett at cox.net>
wrote:
>Glen Starrett wrote:
>> Tony -- Will this be something that's fixed quickly? I'm anxious to get
>> updated to the latest stable in order to restore the taginfo
>> functionality (and stay on the supported release), but I don't want to
>> update the server so frequently.
>
>This might also be something that is handled by a modification to the
>CVSMailer script, perhaps by adding a %t to the mailer command line. I
>don't know if that would work though because there's no documentation on
>the taginfo script in the online version of the manual
>(http://www.cvsnt.org/manual/html/), but looking at loginfo it might work.
It is possible, by doing a mod to the script such that the last
parameter becomes %{sVvt}.
It gives the CVSMailer a command line parameter that contains
individual tag values for each file as follows (wrapped line):
Parameter 5: ModuleXX ModuleXXdoc.txt,1.68,1.68.2.1,Branch_Tst4
SecondFile.txt,1.20,1.20.2.1,Branch_Tst3 ThirdBranchFile.txt,1.2,1.3,
ThirdFile.txt,1.11.2.2,1.11.2.3,Branch_MergeTest
But the downside is that this will enlarge the command line, possibly
very much so and this in turn can trigger the Windows limitation to
the length of the command line that originally forced us to move the
list of tagged files for taginfo from command line to STDIN.
So it is not really a viable way.
Tony apparently has done something in the source tree now, but I can
no longer build cvsnt reliably so I have to wait for a binary posting
before I can verify if this has solved the problem.
And while looking for this I found the potentially more serious bug in
the Entries files handling (see my other thread today)...
/Bo
(Bo Berglund, developer in Sweden)