Hmm...  just tried without -m, using vi instead.  Still works for me. 
Very strange...

Instead of "cvs up -PRd" an existing checkout, try a fresh "cvs co
...".  should work either way, but hey..?


On 2/20/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> With -m "..." it works, but when editor is used it does not, strange
>
> Stephen Deasey wrote:
> > On 2/20/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> >> Believe today is not the first day i use cvs, i even pasted 3 times what
> >> i put in the ChangeLog and still i got error: message is too short.
> >
> > Your message is too short.
> >
> >
> > $ cvs co test
> > cvs checkout: Updating test
> > U test/foo
> >
> > $ cd test
> > $ echo bar > foo
> >
> > $ cvs commit -m "short"
> > cvs commit: Examining .
> > error: Commit message too short.
> > cvs [commit aborted]: Message verification failed
> >
> > $ cvs commit -m "too short"
> > cvs commit: Examining .
> > error: Commit message too short.
> > cvs [commit aborted]: Message verification failed
> >
> > $ cvs commit -m "still too short"
> > cvs commit: Examining .
> > error: Commit message too short.
> > cvs [commit aborted]: Message verification failed
> >
> > $ cvs commit -m "Demonstrating accurate commit messages."
> > cvs commit: Examining .
> > Checking in foo;
> > /cvsroot/naviserver/test/foo,v  <--  foo
> > new revision: 1.2; previous revision: 1.1
> > done
> >
> >
> > Works for me.
> >
> >
> >> SF CVS behaves strange lately
> >>
> >> Stephen Deasey wrote:
> >>> After you type "cvs commit" and vi pops up, what are you typing as
> >>> your commit message?
> >>>
> >>> If you're leaving this blank or typing "See ChangeLog", I'll box your 
> >>> ears :-)
> >>>
> >>>
> >>> After you next "cvs co ..." you should see the following in the
> >>> message template:
> >>>
> >>> CVS: 
> >>> ----------------------------------------------------------------------
> >>> CVS:
> >>> CVS: Did you follow these steps?
> >>> CVS:
> >>> CVS:   1) Examine the changes you are about to commit: cvs diff -uN | less
> >>> CVS:
> >>> CVS:   2) Describe your change in the ChangeLog before commiting.
> >>> CVS:
> >>> CVS:   3) Paste the ChangeLog message into the space above as your
> >>> CVS:      commit message, including the files you touched.
> >>> CVS:
> >>> CVS:
> >>> CVS: 
> >>> ----------------------------------------------------------------------
> >>> CVS: Enter Log.  Lines beginning with `CVS:' are removed automatically
> >>> CVS:
> >>> CVS: Committing in .
> >>> CVS:
> >>> CVS: Modified Files:
> >>> CVS:
> >>> CVS: ...
> >>>
> >>>
> >>> On 2/20/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> >>>> For some reasons CVS started failing with error
> >>>>
> >>>> error: Commit message too short.
> >>>>
> >>>> or empty message.
> >>>>
> >>>> I cannot commit anymore.
> >>>>
> >>>> --
> >>>> Vlad Seryakov
> >>>> 571 262-8608 office
> >>>> [EMAIL PROTECTED]
> >>>> http://www.crystalballinc.com/vlad/
> >>>>
> >>>>
> >>>> -------------------------------------------------------
> >>>> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> >>>> files
> >>>> for problems?  Stop!  Download the new AJAX search engine that makes
> >>>> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> >>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> >>>> _______________________________________________
> >>>> naviserver-devel mailing list
> >>>> [email protected]
> >>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >>>>
> >>>
> >>> -------------------------------------------------------
> >>> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> >>> files
> >>> for problems?  Stop!  Download the new AJAX search engine that makes
> >>> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> >>> http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> >>> _______________________________________________
> >>> naviserver-devel mailing list
> >>> [email protected]
> >>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >>>
> >>
> >> --
> >> Vlad Seryakov
> >> 571 262-8608 office
> >> [EMAIL PROTECTED]
> >> http://www.crystalballinc.com/vlad/
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> >> files
> >> for problems?  Stop!  Download the new AJAX search engine that makes
> >> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> >> _______________________________________________
> >> naviserver-devel mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >>
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> > _______________________________________________
> > naviserver-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >
>
>
> --
> Vlad Seryakov
> 571 262-8608 office
> [EMAIL PROTECTED]
> http://www.crystalballinc.com/vlad/
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>

Reply via email to