From: Heiko Voigt <hvoigt@hvoigt.net>
To: Jon Brisbin <jon.brisbin@npcinternational.com>
Cc: git@vger.kernel.org
Subject: Re: How to move users from SEU (AS400) to Git?
Date: Tue, 12 May 2009 18:14:56 +0200 [thread overview]
Message-ID: <20090512161456.GB21556@macbook.lan> (raw)
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
next prev parent reply other threads:[~2009-05-12 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:42 How to move users from SEU (AS400) to Git? Jon Brisbin
2009-05-12 15:57 ` Shawn O. Pearce
2009-05-12 16:14 ` Heiko Voigt [this message]
2009-05-12 16:16 ` Andreas Ericsson
2009-05-12 16:47 ` Mike Ralphson
2009-05-12 16:40 ` Mike Ralphson
2009-05-12 17:56 ` Jon Brisbin
2009-05-12 18:13 ` Magnus Bäck
2009-05-12 18:20 ` Jon Brisbin
2009-05-12 21:31 ` Ealdwulf Wuffinga
2015-12-02 18:09 ` dleong
2015-12-02 18:22 ` Randall S. Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090512161456.GB21556@macbook.lan \
--to=hvoigt@hvoigt.net \
--cc=git@vger.kernel.org \
--cc=jon.brisbin@npcinternational.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).