如何在拇指驱动器上使用工作目录时安全地使用VSS?

时间:2022-12-01 11:28:52

I know putting code into VSS in general is as safe as putting money into a mutual fund run by Bernard Madoff, but I don't have the luxury of ditching it for subversion.

我知道将代码放入VSS通常与将资金投入由Bernard Madoff运营的共同基金一样安全,但我没有把它放弃颠覆的奢侈。

That said, I need to be able to write code on two machines, I'm considering checking out code to a flash thumb drive.

也就是说,我需要能够在两台机器上编写代码,我正在考虑将代码签出到闪存拇指驱动器上。

Anyone know in advance what I should/shouldn't do to avoid loss of work? Do I need to ensure the drive letter stays the same?

任何人都事先知道我应该/不应该做些什么以避免失去工作?我是否需要确保驱动器号保持不变?

2 个解决方案

#1


Shouldn't be any different than if you checked it out to a mounted drive within the machine. As far as the OS is concerned, the thumb drive is just like your HDD, just slower.

与检查机器内已安装的驱动器的情况不应该有任何不同。就操作系统而言,拇指驱动器就像你的硬盘驱动器一样慢。

#2


I don't know about the specific question you're asking. I suspect that it would be fine if you kept the drive letter consistent between the two machines. I would question whether you really need to access VSS from both machines anyway.

我不知道你问的具体问题。我怀疑如果你保持两台机器之间的驱动器号一致就没问题。我会怀疑你是否真的需要从这两台机器*问VSS。

However, if you're concerned about potential loss of work, it would make more sense to me to check in your changes when you're done working on computer A, so that you can then check out the files on computer B, and vice versa. Otherwise, the implication is that you would have un-checked-in changes on the thumb drive which could easily be lost in transit.

但是,如果您担心可能会丢失工作,那么当您在计算机A上工作时检查您的更改会更有意义,这样您就可以检查计算机B上的文件,以及副本反之亦然。否则,暗示您将在拇指驱动器上进行未经检入的更改,这些更改很容易在传输过程中丢失。

You should create a dedicated branch of your project so you can check-in partially complete changes without breaking anyone else's build.

您应该创建项目的专用分支,以便您可以签入部分完成的更改,而不会破坏其他人的构建。

#1


Shouldn't be any different than if you checked it out to a mounted drive within the machine. As far as the OS is concerned, the thumb drive is just like your HDD, just slower.

与检查机器内已安装的驱动器的情况不应该有任何不同。就操作系统而言,拇指驱动器就像你的硬盘驱动器一样慢。

#2


I don't know about the specific question you're asking. I suspect that it would be fine if you kept the drive letter consistent between the two machines. I would question whether you really need to access VSS from both machines anyway.

我不知道你问的具体问题。我怀疑如果你保持两台机器之间的驱动器号一致就没问题。我会怀疑你是否真的需要从这两台机器*问VSS。

However, if you're concerned about potential loss of work, it would make more sense to me to check in your changes when you're done working on computer A, so that you can then check out the files on computer B, and vice versa. Otherwise, the implication is that you would have un-checked-in changes on the thumb drive which could easily be lost in transit.

但是,如果您担心可能会丢失工作,那么当您在计算机A上工作时检查您的更改会更有意义,这样您就可以检查计算机B上的文件,以及副本反之亦然。否则,暗示您将在拇指驱动器上进行未经检入的更改,这些更改很容易在传输过程中丢失。

You should create a dedicated branch of your project so you can check-in partially complete changes without breaking anyone else's build.

您应该创建项目的专用分支,以便您可以签入部分完成的更改,而不会破坏其他人的构建。