Timeline for Preventing conflicting simultaneous edits
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 24, 2009 at 12:04 | vote | accept | Sampson | ||
| Dec 30, 2013 at 22:01 | |||||
| Jul 17, 2009 at 13:24 | comment | added | devinb | @Marc, I've unfortunately never had the pleasure of working with Visual SourceSafe. I've been spoiled by TFS for my working career. I shudder to think of going back to the dark ages prior to it. Zip Files as source control. | |
| Jul 17, 2009 at 13:20 | comment | added | Marc Gravell | @devinb - you've seen Visual SourceSafe, I take it? ;-p | |
| Jul 17, 2009 at 13:09 | comment | added | devinb | @Jonathan, like source control, it doesn't care HOW MANY edits have been made since, it only cares about the edit you tried to make and the current server version. If four people are currently editing, then one checks in, no problem, a second checks in, and merges against the first 'check-in', a third checks in, and merges against the second check-in, etc. Source control would be terrible if only one person were ever allowed to edit the source code at a time. | |
| Jul 17, 2009 at 12:46 | comment | added | Sampson | I'm worried what the 'merge,overwrite,discard' screen would look like if say 3 or 4 people were making simultaneous edits. | |
| Jul 17, 2009 at 12:32 | history | answered | devinb | CC BY-SA 2.5 |