Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

CVS Bug: cvs [commit aborted]: cannot specify both a message and a log file

17 views
Skip to first unread message

YAW JIUN TAN

unread,
Dec 11, 2018, 8:59:07 AM12/11/18
to bug...@nongnu.org
Hi Folks,

I'm having a problem with this CVS error message. I'm wondering is there a
solution or workaround on this?

>> cvs commit -F MSGFILE

>> cvs [commit aborted]: cannot specify both a message and a log file


Cheers,
YawJiun
TDTI

Mark D. Baushke

unread,
Dec 11, 2018, 7:31:01 PM12/11/18
to YAW JIUN TAN, bug...@nongnu.org
Hi YawJiun,

YAW JIUN TAN <yawji...@globalfoundries.com> writes:

> I'm having a problem with this CVS error message. I'm wondering is there a
> solution or workaround on this?
>
> >> cvs commit -F MSGFILE
>
> >> cvs [commit aborted]: cannot specify both a message and a log file

This error should only happen when you specify both the -m 'message'
and -F logfile options on the cvs commit command-line.

The error occurs in the src/commit.c::commit() function.

-- Mark

YAW JIUN TAN

unread,
Dec 11, 2018, 8:08:19 PM12/11/18
to bug...@nongnu.org, m...@gnu.org
Hi Mark,

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

Cheers,
YawJiun
TDTI

Mark D. Baushke

unread,
Dec 11, 2018, 8:58:51 PM12/11/18
to YAW JIUN TAN, bug...@nongnu.org
Hi YawJiun,

YAW JIUN TAN <yawji...@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

YAW JIUN TAN

unread,
Dec 12, 2018, 1:57:34 AM12/12/18
to bug...@nongnu.org, m...@gnu.org
Hi Mark,

Ok thanks for your comments. Appreciate it.

Cheers,
YawJiun
TDTI
0 new messages