[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Question about the command-line for committing
From: |
Paul Sander |
Subject: |
Re: Question about the command-line for committing |
Date: |
Thu, 11 Jan 2001 09:43:03 -0800 |
Have you looked into using Expect to automate such a test? With it, you
can script interactions with your editor. Perl also has a module that
provides similar behavior.
--- Forwarded mail from address@hidden
The "commit" command of CVS has an option, "-m", for specifying a log
message on the command-line instead of interactively using an editor. But
what happens when the commit is recursive and there are files in other
directories that will be committed? Is there a way to specify (on the
command-line) different log messages for different directories?
While this question seems to be irrelevant (why would a user want to specify
different log messages to different directories through the command-line?),
I am interested in this for testing purposes -- I have set up some scripts
to handle commit commands using the "loginfo" and "commitinfo" files in the
repository, and I would like to have an automatic script to test them. One
of my test cases is providing a different log message for each directory,
and if I can't do that from the command-line then this test case has to be
manual (at least partially - I will need to wait for the editor and enter
the log message).
--- End of forwarded message from address@hidden