version control - How to actually work with Git in a concurrent enviornment -
so, migrating cvsnt perforce or git, , i've been studying features in last weeks, , clear me perforce bit more similar since centralized.
git seems fast, company developers stay in same room, though there's on 100 developers, still computers connected cvsnt server...
for reason, can't see how adapt git work perforce do..
for being offline, when 1 clones git repository, copy history , repository have working offline, however, working in concurrent way, seems weird have local file's history example...
so if developer b commits , push server, developer won't know it, won't in file's history...unless pulls server, right?! (as long in same branch..)
but if works way, i'd working in centralized way distributed scm...and have 'guess' when 1 has pushed server.. if there's command know if file has new revision, bad having check manually..
can explain me better how git can work in concurrent way without 1 having know when other push server, etc..?
another thing, couldn't find nice revision graph on git, i've found in tortoise git, more branch graph revision's graph..
the usual workflow dvcs git doesn't rely on guessing if has push or not.
you push, , if else has pushed before you, your action be, default, denied (as being not "fast-forward").
then pull:
- ideally,
git pull --rebase
in order redo work on top of recent commits of branch). - you check if everthing still works
- you push back
as revision graph, simple git log --graph
can see going on (i like alias).
Comments
Post a Comment