git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to move users from SEU (AS400) to Git?

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
May 12, 2009, 16:14 UTC
Message-ID
<20090512161456.GB21556@macbook.lan>
In-Reply-To
<1CA7E776-B216-4AA5-BFE0-63C0B066980D@npcinternational.com>
On Tue, May 12, 2009 at 10:42:32AM -0500, Jon Brisbin wrote:
> I'm just wondering what the Git experts would say to someone wanting to 
> transition from say, Visual SourceSafe, and expecting the predictability 
> of having source files "locked out" while a developer is making changes 
> to them?
How about this:

With Git you effectively get a *local lock* on *all files*. These locks are just called branches. Thus you do not have to worry about anything getting lost (like it could happen with the svn/cvs update command).

To unlock you merge. If you merge two branches and something (although unlikely) goes wrong you can always return to the "different locked states" and investigate.

Seen this way git is the best from both worlds (lock/merge).
cheers Heiko
Previous: Shawn O. PearceNext: Andreas Ericsson
Message 3 of 12 in “How to move users from SEU (AS400) to Git?”
  1. Jon BrisbinMay 12, 2009
  2. Shawn O. PearceMay 12, 2009
  3. Heiko VoigtMay 12, 2009
  4. Andreas EricssonMay 12, 2009
  5. Mike RalphsonMay 12, 2009
  6. Mike RalphsonMay 12, 2009
  7. Jon BrisbinMay 12, 2009
  8. Magnus BäckMay 12, 2009
  9. Jon BrisbinMay 12, 2009
  10. Ealdwulf WuffingaMay 12, 2009
  11. dleongDec 2, 2015
  12. Randall S. BeckerDec 2, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.