1
0
mirror of https://github.com/git/git.git synced 2024-11-18 02:14:03 +01:00

CVS-like push-pull description update.

- Yes, push does not lock, but that does not mean it is not
   meant for multi-user repository.  It just ought to perform
   correctly without using locks.

 - Let's not pretend we know _the_ right way.

Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
Junio C Hamano 2005-08-01 12:33:05 -07:00
parent 7da71deb11
commit 3206014a51

@ -111,17 +111,15 @@ repository of this person public, and make every team member
pull regularly from it.
2. Set up a public repository with read/write access for every team
member. Use "git pull/push" as you used "cvs update/commit". Beware!
Linus says that "git push" does no locking, since it was not meant
for multi-user repositories!
member. Use "git pull/push" as you used "cvs update/commit". Be
sure that your repository is up to date before pushing, just
like you used to do with "cvs commit"; your push will fail if
what you are pushing is not up to date.
3. Make the repository of every team member public. It is the
responsibility of each single member to pull from every other
team member.
4. Read Documentation/tutorial.txt and admit that the described work
flow is the best.
CVS annotate
------------