<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I have been struggingly to do anything with git.<br>Just me?<br>Please help?<BR> <BR> <BR>I understand that everyone gets a copy of the repository, so viewing history<br>is fast and disconnected.<BR> <BR> <BR>I understand I get to commit locally so that I can commit willy nilly and nobody<br>will notice or mind.<BR> <BR> <BR>I understand that after I commit locally willy nilly, I can "combine" many<br>small commits into one commit, so that when eventually my changes are shared,<br>while the history might be hierarchical/branched, it won't be too noisy.<BR> <BR> <BR>Those are all good selling points.<BR> <BR> <BR>Now, things I don't understand.<BR> <BR> <BR>Besides my local repository, is github also hosting a fork just for me?<BR> <BR> <BR>I commit to that "somewhat willy nilly"?<BR>This seems like a somewhat redundant extra layer.<BR> <BR> <BR>And then, "third level of the hierarchy", occasionally my github<br>repository is merged with the master?<BR> <BR> <BR>I submit a pull request?<br>I haven't figured out how.<BR>And who handles them?<BR>Or it is automatic? But how to stop arbitrary edits then?<BR>i.e. how to approve people?<BR> <BR> <BR>There is more I don't understand.<br>Like, in CVS and Perforce I am accustomed to multiple clients/checkouts/enlistments,<br>for separate work, or for "buddy builds".<BR> <BR> <BR>But that shouldn't require a whole additional repository full of history.<BR> <BR> <BR>What is the analog in Git?<BR> <BR>Alternatively, can some write up the following workflows:<BR><br> 1. start from scratch<br> 2. get a file edited in the mainline<br> 3. and then undone <BR><br> 1. start from scratch<br> 2. get a file added in the mainline.<br> 3. and then edited <BR> <BR><br>So much documentation talks about tangential scenarios, like "git init" which I don't think is relevant.<BR> <BR> also, I find git status is quite slow. <br> So much for offline and disconnected. <br> Is there a mode where, like: <br> 1) files are read only by default <br> 2) I have to run git to make them writable <br> 3) It will remember, quickly? <BR> <BR>I am thoroughly familiar with and happy with perforce, so explanations<br>that attempt to compare/contract/reuse-vocabulary with it are welcome.<BR> <BR> <BR>Thanks,<br> - Jay<br><br> <BR> </div></body>
</html>