Changes between Version 30 and Version 31 of Git/GitHome


Ignore:
Timestamp:
Oct 28, 2016, 4:35:59 PM (2 years ago)
Author:
Stefan Seefeld
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Git/GitHome

    v30 v31  
    22[[BR]]
    33
    4 = Getting Started with Git =
     4This page is superseded by https://github.com/boostorg/boost/wiki/Getting-Started-With-Git
    55
    6 [[PageOutline]]
    7 
    8 Being able to use the Git version control system is a prerequisite for working with the Modular Boost repositories. This page gets you started!
    9 
    10 For specific instructions on trying modular boost: [[TryModBoost]].
    11 
    12 == Required Git Release ==
    13 
    14 '''1.7.3''' or later.
    15 
    16 To find the version number of Git once it is installed, do this from the default command line for your system:
    17 
    18 {{{
    19 git --version
    20 }}}
    21 
    22    ''Other command line processors will probably work, but we only test with the default, such as {{{bash}}} on Linux, and {{{cmd.exe}}} on Windows.''
    23 
    24 If you have an earlier Git release installed, please upgrade it.
    25 
    26 == Installing Git ==
    27 
    28 || If you plan to do the [http://gitimmersion.com/ Git Immersion Tutorial], it includes links to installation downloads. ||
    29 
    30 [http://git-scm.com/downloads Downloads] are available for various platforms.
    31 
    32 === Windows ===
    33 
    34 [http://code.google.com/p/tortoisegit/ TortoiseGIT], a port of TortoiseSVN, is recommended for Windows users who prefer a GUI interface or already use TortoiseSVN.
    35 
    36   **Windows hint:** If you install TortoiseGIT, avoid incompatibilities by using the Windows command line version of Git that TortoiseGIT installs. I.E. place {{{C:\Program Files (x86)\Git\cmd}}} in your path ahead of any other git binaries, such as those cygwin might install. While in theory you could run git from bash, Windows Powershell, or other shells, examples in these Boost documentation pages are tested only with the regular Windows command line, {{{cmd.exe}}}.
    37 
    38   **Windows hint:** To generate !GitHub SSH authentication keys, as described in [https://help.github.com/articles/generating-ssh-keys#platform-windows GitHub help], be sure to use {{{"C:\Program Files (x86)\Git\Git Bash"}}}. Otherwise the {{{.ssh}}} directory may not get generated in your HOMEPATH directory, and !GitHub authentication will fail.
    39 
    40 === Unix, Linux, etc. ===
    41 
    42 [https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools#Graphical_Interfaces Linux GUI interfaces] are enumerated at the wiki page for GIT.[[BR]]
    43 
    44 ''gitk'' and ''git gui'' are the most responsive and common tools. To start using them just execute "gitk ." (without quotes) in folder with cloned GIT repo. ''git gui'' can be started from ''gitk'', via "File"->"Start git gui".
    45 
    46  **Linux hint:** You need to create SSH keys and add them to your git account, as described in [https://help.github.com/articles/generating-ssh-keys GitHub help]
    47 
    48 === Mac OS X ===
    49 
    50 == Learning to use Git ==
    51 
    52 You need to learn how to use Git from the command line even if you plan to use Git via a graphical client or your IDE:
    53  * Learning and other communication about Git almost invariably uses CLI commands to describe a Git operation.
    54  * You will need use the command line to read or write scripts involving git.
    55 
    56 Recommended learning and reference resources:
    57 
    58 * [http://www.youtube.com/user/github Git and GitHub Videos] Interesting and authoritative, as you would expect from Scott Chacon.
    59 * [http://gitimmersion.com/ Git Immersion Tutorial] A deep dive into Git.
    60 * [http://gitref.org Git Quick Reference]. "... a quick reference for learning and remembering the most important and commonly used Git commands."] Recommended for those who like to cut to the chase. Examples use a POSIX style command line interpreter, but Git works identically under the Windows command line so that should not be a problem for most Boost developers.
    61 * [http://git-scm.com/book Pro Git]. Scott Chacon's online book is recommended both for learning about Git and as a reference.
    62 * [http://www.youtube.com/watch?v=GYnOwPl8yCE Power Your Workflow With Git]. Patrick Hogan's video introduction to Git and GitFlow-based workflow. Recommended for those who want to know what is going on under the covers, why Git is the way it is, and recommended workflows. The [http://www.slideshare.net/pbhogan/power-your-workflow-with-git slides] are also available.
    63 * The [StartModWorkflow Getting Started with Modular Boost Library Development using Git] page has links related to Git Flow, the recommended workflow for Boost library developers.
    64 
    65 == Git Topics ==
    66 
    67 * [wiki:WhyGit Why should Boost move to Git?] Provides the rationale for moving to Git.
    68 
    69 == Git Links ==
    70 
    71 * [http://git-scm.com/ Git's official website].
     6'''Please help''' migrate the rest of the old wiki !