Lines Matching refs:commit

40     and specified to commit.
241      file, non-interactively before the commit, such that a single, fully
242      recursive commit prompts for one commit message, and concatenates the
243      per file messages for each file.  In short, one commit, one editor
244      session, log messages allowed to vary across files within the commit.
246      files are changed, which may predate the commit considerably.
256      The text is saved as CVS/foo.c,m (or some such name) and commit
258      message specified at commit time.  Easy enough.  (having cvs
259      commit be non-interactive takes care of various issues like
261      message (see comment in commit.c at call to start_server).  Also
263      do_editor if the up-to-date check fails (see commit.c client code).
265      I'm not sure about the part above about having commit prompt
266      for an overall message--part of the point is having commit
282      commit (probably run "cvs message" again, as hinted in (1))?
290      commands.  In particular, for "commit" and "import", where one would
300 154. When committing the modules file, a pre-commit check should be done to
313      {commit,rcs,log}info files? It would probably be useful with all of
317 158. If I do a recursive commit and find that the same RCS file is checked
319      files (but within the realm of a single "commit"), CVS will commit the
324 160. The checks that the commit command does should be extended to make
328      forward after the commit.
596     commit.c: failed to remove tag `%s' from `%s' (Questionable.
600     commit.c: failed to commit dead revision for `%s' (likewise)
730 commit").
830 228.  Consider adding -d to commit ala ci.