Re: Major bug in VS 2008 source code control
- From: David Connet <stuff@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 18 Jun 2008 17:30:43 GMT
David Thielen <thielen@xxxxxxxxxxxxx> wrote in
news:ahuf54tlumbs11b6b12a6gfsqf4uu4ftro@xxxxxxx:
Hi;
One of our developers had a file that they did NOT check out. They
edited it and saved the changed file on their system.
To get back to the correct file they did a "get latest." Get latest
said that they already had the most recent version and did not bring
down the correct file.
How can we use "get latest" to pull down the latest version if that is
not what we have on disk? We have to have this functionality as
otherwise developers will have to compare files 1 by 1 to make sure
they have the latest version.
I wouldn't call that a major bug in the source control system - it's a
bug in your process.
One of two things is probably going on (depending on the source control
system):
- The file on the server hasn't changed, there for the local file is
current. (things like CVS, SVN can work like this)
- The source system doesn't know the local file has changed (the system
"knows" what you have). Perforce (what we use) is like this. So it has no
reason to update anything. (these systems usually have an option
somewhere that says 'ignore what you think I have and update anyways')
For systems like the later, what I find best is to make non-checked out
files readonly. If you change that and edit the file anyways, well that's
your problem! And if the server file changes, you could lose any changes
you've done.
Dave Connet
.
- Follow-Ups:
- Re: Major bug in VS 2008 source code control
- From: David Thielen
- Re: Major bug in VS 2008 source code control
- References:
- Major bug in VS 2008 source code control
- From: David Thielen
- Major bug in VS 2008 source code control
- Prev by Date: Re: VS 2008 source code control questions
- Next by Date: How do I have VS 2005 Team Edition connect to our VS 2008 TFS server source code control?
- Previous by thread: Major bug in VS 2008 source code control
- Next by thread: Re: Major bug in VS 2008 source code control
- Index(es):
Relevant Pages
|
Loading