Groups | Search | Server Info | Login | Register
| From | YAW JIUN TAN <yawjiun.tan@globalfoundries.com> |
|---|---|
| Newsgroups | gnu.cvs.bug |
| Subject | Re: CVS Bug: cvs [commit aborted]: cannot specify both a message and a log file |
| Date | 2018-12-12 14:57 +0800 |
| Message-ID | <mailman.5622.1544597853.1284.bug-cvs@nongnu.org> (permalink) |
| References | <CA+41pcMXCpBpgFPmYLqiB3VSr6mimsux3oevtJFFwW2R=JVruw@mail.gmail.com> <5637.1544573743@contrail-ubm16-mdb.svec1.juniper.net> <CA+41pcP0NgCKDg5SToxnyCL=6-yYF6HV-af1k3a18SW=DMy-xw@mail.gmail.com> <7591.1544579009@contrail-ubm16-mdb.svec1.juniper.net> |
Hi Mark, Ok thanks for your comments. Appreciate it. Cheers, YawJiun TDTI On Wed, Dec 12, 2018 at 9:43 AM Mark D. Baushke <mdb@gnu.org> wrote: > Hi YawJiun, > > YAW JIUN TAN <yawjiun.tan@globalfoundries.com> writes: > > > Thanks for your prompt reply. > > > > I didn't specify the -m 'message' in my command. I'm just running with -F > > logfile as shown below. The error is an intermittent error. So I > wondering > > is this a bug and any workaround being discussed before? > > > > >> cvs commit -F logfile > > I have not really seen this before in either the 11.x or 12.x versions > of CVS. > > It may be possible that one of the 'trigger' scripts might be doing > something odd, but that would depend on how your CVS is configured. > > The CVS sources are public you could modify a local copy to add more > information to the commit() function if you think it would help you > narrow down the problem. Possibly writing into a file in /tmp/ or some > such that may be viewed only after you note the error arising again. > > Good luck, > -- Mark >
Back to gnu.cvs.bug | Previous | Next | Find similar
Re: CVS Bug: cvs [commit aborted]: cannot specify both a message and a log file YAW JIUN TAN <yawjiun.tan@globalfoundries.com> - 2018-12-12 14:57 +0800
csiph-web