我们可以提交单独的文件吗?

发布于 2024-09-11 20:37:43 字数 232 浏览 4 评论 0原文

您好,我们正在使用 CVS 并且定期进行开发。大多数时候我只处理一到三个文件。我仍然需要提交文件夹中的所有更改吗?是否可以选择必须提交的文件并且不允许 CVS 提交仍在开发中的文件?

与文件 1、文件 2 和文件 3 一样......我一天的大部分时间都在使用文件 1,我检查日志并在文件 2 中遇到一些问题,因此我对文件 2 进行了快速更改并决定提交。但 file 中的代码仍在开发中,只想提交对 file2 所做的更改。这可能吗?

Hello we are using CVS and development takes place regularly. I work only on one-three files most of the time. Do I still have to commit all the changes in the folder?? Is it possible to select the files which have to be committed and not allow the CVS to commit files which are still in development??

As in file 1, file 2 and file 3....I work with file 1 for most of the day, I check the logs and have some problem in file 2, so I make a quick change in file 2 and decide to commit. But code in file is still in development and only want to commit changes made to file2. Is that possible?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

碍人泪离人颜 2024-09-18 20:37:44

是的,只需使用

cvs commit file2

Yup, just use

cvs commit file2
何时共饮酒 2024-09-18 20:37:44

取自 http://cvsbook.red-bean.com/cvsbook.html

"在这里,我们按名称提交一个文件,并按推理提交两个文件:”

 floss$ cvs commit -m "print goodbye too" hello.c
 Checking in hello.c;
 /usr/local/cvs/myproj/hello.c,v  <--  hello.c
 new revision: 1.2; previous revision: 1.1
 done
 floss$ cvs commit -m "filled out C code"
 cvs commit: Examining .
 cvs commit: Examining a-subdir
 cvs commit: Examining a-subdir/subsubdir
 cvs commit: Examining b-subdir
 Checking in a-subdir/subsubdir/fish.c;
 /usr/local/cvs/myproj/a-subdir/subsubdir/fish.c,v  <--  fish.c
 new revision: 1.2; previous revision: 1.1
 done
 Checking in b-subdir/random.c;
 /usr/local/cvs/myproj/b-subdir/random.c,v  <--  random.c
 new revision: 1.2; previous revision: 1.1
 done
 floss$

Taken from http://cvsbook.red-bean.com/cvsbook.html

"Here, we commit one file by name and two by inference:"

 floss$ cvs commit -m "print goodbye too" hello.c
 Checking in hello.c;
 /usr/local/cvs/myproj/hello.c,v  <--  hello.c
 new revision: 1.2; previous revision: 1.1
 done
 floss$ cvs commit -m "filled out C code"
 cvs commit: Examining .
 cvs commit: Examining a-subdir
 cvs commit: Examining a-subdir/subsubdir
 cvs commit: Examining b-subdir
 Checking in a-subdir/subsubdir/fish.c;
 /usr/local/cvs/myproj/a-subdir/subsubdir/fish.c,v  <--  fish.c
 new revision: 1.2; previous revision: 1.1
 done
 Checking in b-subdir/random.c;
 /usr/local/cvs/myproj/b-subdir/random.c,v  <--  random.c
 new revision: 1.2; previous revision: 1.1
 done
 floss$
玩世 2024-09-18 20:37:44

除了其他人所说的(这是正确的答案)之外,为什么不为实验性的东西创建一个分支,而不是推迟提交更改呢?

Alternatively to what the others said (which is the correct answer), instead of holding back to commit changes, why not create a branch for the experimental stuff?

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文