Lines Matching refs:commit
184 attached to a real RCS branch. When you commit a file to a
221 When you want to be able to "commit" and "tag" your work repeatedly
283 Between steps 1 & 2 you may commit changes. The result would be same
312 that allows you to "checkout" the branch, to "commit" files to the end
460 you must commit them.
525 cvs commit
773 cvs commit <<== Onto branch
785 cvs commit
806 cvs commit <<== Onto branch
823 cvs commit
826 cvs commit
835 Repository while you do this. If they commit something while you are
873 be able to commit until you again move forward to the end of
881 As in #1, you can't commit to this kind of working area,
971 cvs commit -m 'Moved branch <branch_tag> onto MAIN'
1081 You don't need to commit something to remember it. The tags you place
1087 copy of it using "cvs update -p" and commit it or use the technique
1348 than "update" and "commit". Even "checkouts" were controlled. This is
1486 You'll have to run "update" before "commit" anyway if there are newer
1886 helps with the update/commit process. When you are ready to update,
1892 possibly from different directories, for commit as a whole.
1895 friendlier and more helpful way to update/commit than raw cvs. One vi
1930 - Optional automatic tagging after each commit.
1961 files you want to edit, and afterwards, commit the changes by typing
1962 "cvs commit".
1999 When you execute "commit", CVS passes the Repository pathname for each
2000 directory (and the files to commit within that directory) to
2001 <command>. If <command> exits with a non-zero status, the commit is
2010 required to enter for each commit.
2016 checking on the commit log.
2061 Use "add" followed by "commit".
2258 as you would if someone else executed "add" and "commit".
2278 When you "commit" a removed file, CVS moves the Repository's matching
2427 Catch invocations of "commit" by defining pre-commit programs in the
2555 When you first "import" or "add"/"commit" a file, the read and execute
2566 "update" (or after a "commit"), your working file is set to match the
2711 revision <X> with a sticky tag of TAG1. The first "commit" to that
2746 revision <X>), but the first commit to the new TAG1 branch will create
2801 finally commit it.
2804 commit as many revisions as you want, then merge it back into the main
2832 moves the RCS default branch on first commit.
2906 The "commit" command retains the timestamp of the file, if the act of
2928 10. While in the middle of a large "commit", how do I run other commands,
2942 active commit. Be careful when creating "patches" from the output of
2953 "cvs -n update" also works in the middle of a commit, providing
3013 Typed the "commit" command in one Repository with your $CVSROOT
3016 "commit" and all other CVS commands will heed an absolute pathname in
3115 before allowing a commit. If any function called from within the
3116 commitinfo file exits with a non-zero status, the commit is denied.
3122 allowed to commit a file? If not, forget commitinfo.
3135 CVS executes the program once for each directory that "commit"
3166 before a commit, the "loginfo" file is used after a commit.
3220 the file to the Repository, you must then "commit" it.
3235 cvs commit <file>
3288 cvs commit <file>
3331 of the "add" command and the expected "commit".
3336 commit uses to check the file in, but CVS itself doesn't put anything
3343 Both files must exist to commit a newly added file. If the
3345 commit. If the ./CVS/file,t file doesn't exist, RCS prints an error
3349 files and rerun the "commit".
3366 cvs commit <file>
3475 idea. You should commit a correction rather than back out a revision.
3482 there. No one cares about simple mistakes -- just commit a corrected
3514 And even worse, if you commit a revision already tagged, you will
3519 that will occur when you commit to this file again, recreating
3547 file. If you then "commit" the file, you will bypass the normal CVS
3548 check for "up-to-date" and will probably commit the revision that was
3553 and "commit" or raw RCS commands) or by applying an editor directly to
3707 Install a pre-commit program in the "commitinfo" file to check for
3716 Make sure the pre-commit program prints a message and exits with a
3717 non-zero status if someone besides the user running "commit" has the
3718 file locked. This non-zero exist status will cause the "commit" to
3721 Make sure the pre-commit program exits with a zero status if the
3722 file is either unlocked or locked by the user running "commit". The
3723 "cvs commit" command that kicked off the pre-commit program will take
3818 " + "commit", "ci", "com""
3820 1. What is "commit" for?
3827 2. If I edit ten files, do I have to type "commit" ten times?
3829 No. The "commit" command will take multiple filenames, directory names
3830 and relative pathnames on the command line and commit them all with
3834 Like all CVS commands, "commit" will work on the whole directory by
3835 default. Just type "cvs commit" to tell CVS to commit all modified
3841 3. Explain: cvs commit: Up-to-date check failed for `<file>'
3843 You may not "commit" a file if your BASE revision (i.e. the revision
3849 "checkout", "update" or "commit". You must now execute "update" to
3851 "commit" will work. You are thus protected (somewhat) from a common
3857 another round of building and testing before the "commit".
3861 4. What happens if two people try to "commit" conflicting changes?
3865 commit the file has no chance of seeing the conflict. Only the second
3902 <previous-rev>" might help here) and commit it on top of the offending
3909 6. Explain: cvs commit: sticky tag `V3' for file `X' is not a branch
3920 the CVS working branch, which is the branch to which "commit" will add
3926 branch is needed. The first commit to a magic branch creates a
3929 You can commit onto the end of the Main Trunk, if you have no sticky
3931 tag. But you can't commit a file that has a sticky tag not pointing to
4003 7. Why does "commit -r <tag/rev>" put newly added files in the Attic?
4012 If you specify "-r <tag>" to commit a newly added file, the <tag> is
4019 In fact, a plain "commit" without the "-r" will throw a newly added
4027 8. Why would a "commit" of a newly added file not produce rev 1.1?
4072 since your last "checkout", "update" or "commit" there is no
4083 "checkout", "update" or "commit"?
4489 "update" (or after a "commit") command, searches for and expands a
4628 (followed by "cvs commit" to make it really take effect) each file
4806 Then, for every file, you'll need to execute "cvs commit".
4841 Keep a list. Suggest a completion date/time. Tell them to "commit" the
4877 Then apply a set of post-commit tags.
4893 <pre-import-tag> <post-commit-tag>". The two sets of differences
5238 do a cvs commit, and then do a _rmdir dir_ in the Repository.
5257 If you executed "remove", but haven't typed "commit" (you can tell
5261 If you followed the "remove" with a "commit", you'll have to move it
5611 5. How do I get "tag" and "rtag" to send mail the way "commit" does?
5613 The "commit" command is supported by two files ("commitinfo" and
5635 string, is that you didn't "commit" your work before "tagging" it.
5708 checkout, update or commit, type:
5772 "checkout", "update" or "commit", into your working files. You can
5827 "checkout", "update" or "commit", nothing will happen.
5877 "edit" in most of the civilized world) and "commit".
5898 commit the file, but is blocked because the file is not up to date.
5905 5555 Change made in the first commit (1.3)
5906 >>>>>>> 1.3 The revision created by the first commit.
5913 Until the conflict is cleared, "commit" is blocked for this file.
5924 After clearing the sticky conflict indicator, you may then commit the
5929 commit is needed.
5931 Forcing the commit to happen by using "commit -f". This is probably
6005 file was moved to the Attic by "commit".
6355 cvs commit <file>
6366 2. If I edit multiple files, must I type "commit" for each one?
6368 No. You can commit a list of files and directories, including relative
6369 paths into multiple directories. You can also commit every modified
6404 since your last checkout, update or commit, type:
6430 cvs commit <file>
6444 since you last executed "checkout", "update" or "commit" into your
6456 since your last "checkout", "update" or "commit", "update" will print
6461 "update" or "commit" of this working file, CVS will remove your
6472 your last "checkout", "update" or "commit"), "update" will print:
6482 last "checkout", "update" or "commit" into your working file. "update"
6495 update or commit) have made changes to the same section of a file, CVS
6613 2. If I work with multiple modules, should I check them all out and commit
6624 them to make and commit changes.
6705 The "diff" and "commit" commands use the sticky tags, unless
6707 you can only "commit" to a file checked out with a sticky tag, if the
6717 The file doesn't exist in the Repository until you "commit" it, but
6736 not commit the same file until "update" has merged the earlier
6741 try to commit your file, CVS says:
6743 cvs commit: Up-to-date check failed for `<file>'
6754 then commit the file. See 3P.6 for info on "sticky conflicts".
6769 And yes, between the time you execute "update" and "commit" (while you
6770 are fixing conflicts and testing the results) someone else may commit
6812 Revision 1.5 (Which you will commit shortly.)
6820 commit the file immediately, #4 and #5 will be the same. But you can
6823 though, you don't need #4 after a commit.
6839 "commit" point, but not forever. You are expected to run the "normal"
6845 committed, under the assumption that you won't commit files until
7001 Executing a CVS command, such as "commit" or "tag" that writes to the
7005 call "commit points", merely stopping the process will not back out
7015 If you interrupt a multi-file "commit" in the middle of
7018 been half-way through the list of files to commit. The
7029 To finish, you can simply retype the same commit command.
7031 commit them. It helps that RCS doesn't leave a file in an
7038 "commit". The RCS file will still be consistent, but
7039 unlike "commit", which only *adds* to the RCS file, "tag"
7083 If you only want to limit "commit" commands, you can write a program
7257 cvs commit <file>
7288 cvs commit <ofile>
7326 add" followed by "cvs commit".
7363 and commit a file in the normal way:
7365 cvs commit <file>
7391 cvs commit
7395 a "commit helper". After a file is committed to such a module,
7453 hand-editing job, not something CVS can handle. Then commit all the
7462 cvs commit
7516 the file. Although it is still possible to commit a file filled with
7847 which you "commit" files.
7896 [Deleted by "commit" or "remove".]
7994 when you include work committed by others. However, you can't commit
8007 individual to commit (and tag) intermediate revisions without changing
8020 developers have continued to commit to the Main line while you are
8224 available to other developers, you "commit" them back into the
8230 may commit the merged result. This method is referred to as
8256 (via the "commit" command) changes or include work committed by others