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.
Hi!
I am using cvsnt 2.0.58d on RHEL3.0 server. I am
trying to use commitinfo utility to catch bad
filenames being created (i.e. spaces in them). Can
someone please provide a bit of information? I have
searched mail archives and not found all my answers.
1) In commitinfo, the following line does not work
right for me:
ALL ~me/bin/chk_spaces %{sVv}
(for now, chk_spaces echos all passed parameters to a
logfile so I can see what is happening)
After doing a commit, my log file contain %{sVV} and
the repo-name/directory of the commit. Calling
chk_spaces rountine with no arguments returns the
repo-name/directory only. Is this expected? How do I
get the name of the file being committed?
2) Commitinfo only works at "commit" time. A bad
filename can be "added" and not caught at add-time.
Yes?
Q: Are there any "add time" trigger methods?
Q: It looks like "adding" only puts line in
CVS/entries file with "dummy timestamp". Someone can
add a file with blanks in the name, cvsnt will accept,
and then when commit is requested, only then will
cvsnt reject the commit. Is this correct?
Q: If developer adds a bad filename, then tries to
commit and is told they cannot commit with blanks in
filename, and they change filename, readd, and then
commit successfully, the CVS/entries file still
contains the bad named file with "dummy timestamp
entry". Will this cause problems?
3) Is there easier way? Has someone already created
commitinfo util that prevents "bad filenames"?
Thank you for any information you can provide.
DC
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com