GithubHelp home page GithubHelp logo

mikemcquaid / gitinpracticeerrata Goto Github PK

View Code? Open in Web Editor NEW
4.0 4.0 1.0 222 KB

๐Ÿ› Errata for Git In Practice

Home Page: https://github.com/MikeMcQuaid/GitInPractice

errata git gitinpractice

gitinpracticeerrata's Introduction

Some things you should know about life:

gitinpracticeerrata's People

Contributors

mikemcquaid avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

todun

gitinpracticeerrata's Issues

possible errata in descriptions of merge conflicts

Since I'm still a Git novice, it's possible that the following is not an error in the text, but is instead simply my failure to understand the concepts fully. Having said that, it seems like the descriptions of merge conflics in Listings 2.11 and 5.7 may be in error.

My understanding is that the text should read:

Listing 2.11
-2 should read 'Current marker'
-3 should read 'Current line'
-5 should read 'Incoming marker'
-6 should read 'Incoming line'

Supporting text for Listing 2.11
-3 should read 'shows a line from the current branch'
-5 should read 'shows a line from the incoming branch'

If this is correct, similar changes would apply to Listing 5.7 and the supporting text.

Chapter 6: Slight Error With Annotations in Listing 6.14

Listing 6.14 which contains the output for rewritten history push failure has the annotations reversed. The annotation labelled 2 Local/remote branches should actually be labelled 1 Local/remote branches and the one labelled 1 push failure should actually be labelled 2 push failure. That way, they match the explanation given below the listing.

Chapter 3: Filesystem interactions (typo)

On page 60,

This interaction between .gitignore and git add is particularly useful when adding
subdirectories of files and directories that may contain files that should to be ignored.

should read

This interaction between .gitignore and git add is particularly useful when adding
subdirectories of files and directories that may contain files that should to be ignored.

Possible typo page 18 section 1.5

The text reads:

This may seen surprising or worrying; after all, didnโ€™t I just tell you
that the history contains the entire list of changes to the project over time?

seen should be seem?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.