ok, looks like I did everything correctly except that I switched directories before i did the git checkout -b branch1 command so I will see what happens next -- i guess i need to specify some files for the new branch (as for item 2. I used SSH).
On Tuesday, April 4, 2017 at 10:03:42 AM UTC-6, Paul Smith wrote: > > What did you do during these 2 days of learning? > > Did you start one of the excellent books on Git, such as the Pro Git > book referred to earlier: https://git-scm.com/book/en/v2 and go through > it step by step? > > Or did you just randomly read man pages etc. and type commands? > > I highly recommend the former. The latter will not be successful, > unless you're already very familiar with SCM tools in general and > distributed SCM tools in particular. > > Another advantage to going through a book like this is it will give you > the terminology you need to ask questions in ways that we can > understand. Many of the questions we see from users take much longer > to solve because the questioner is using incorrect terms, so there's a > lot of back and forth between us trying to work out exactly what > they're asking. > > Finally, when asking for help please provide EXACT commands you typed > and EXACT error messages/results you received. You can modify things > to be more private (for example you can change the hostname of your > server to "my.host.com" or something like that) but having the exact > commands is critical to determining errors. > > > On Tue, 2017-04-04 at 05:25 -0700, bestbrightes...@gmail.com <javascript:> > wrote: > > 1. I'm in the path ../bitbucket/source (remote repo) > > You should absolutely, positively NOT be in the "remote repo" when you > make a clone! > > In Git you are in the location where you want to create the clone, and > you provide the clone command the name of the remote repository you > want to clone. > > > 2. I did the command: git clone with a path > > So, you access the remote repository via a path, not over SSH or HTTPS > or some other protocol? > > > 3. It replies Cloning into 'whatever' ... > > 4. It replies Checking out files: 100% (6140/6140), done > > 5. I then went to path /bitbucket/sourcecode (localhost repo) > > 6. Entered the command: checkout -b branch1 > > 7. This replies back (many files) needs merge > > Suppose your repo is available to you via a path like > "/remote/repo.git" and your home directory is something like > "/home/me". > > Then I suggest you create your clone like this: > > cd /home/me > git clone /remote/repo.git > > It will choose a default name of the repo for you, or you can provide > one specifically if you prefer: > > git clone /remote/repo.git repo > > Now you can change to your clone of the repo: > > cd /home/me/repo > > and see all your files. If you run "git status" you should see you > have no modified files. > > Now to make a new branch such as "my/branch1" you would run: > > git checkout -b my/branch1 > > "git status" should again show that you have no files modified. > > Now if you change a file and run "git status", it will show that file > as modified. > > If you can get this far, then you should be back on track. If there > are specific problems please ask them by providing the exact command > and exact output using cut and paste, not paraphrased abstract > commands. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
