Steve Litt <slitt@???> writes:

>>       From: Steve Litt <slitt@???>
>>  Subject: Re: [DNG] Debianising my uploaded version of netman.

>>
>
>> Anyone know a good source of GIT learning that's self-discoverable and
>> has a reasonable learning curve from know-nothing to expert?
>
>
> On Wed, 9 Dec 2015 16:57:01 +0000 (UTC)
> dan pridgeon <d_pridge@???> wrote:
>
>> This may help:
>> http://git-scm.com/book/en/v2 
>
> Very nice! I've read a few pages, and so far, this appears to be
> *exactly* what I needed.

It's presumably rather "what you're supposed to get", considering
howlers like

    This is in sharp contrast to the way most older VCS tools
    branch, which involves copying all of the project’s files into a
    second directory.
        http://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell

CVS creates branches by adding special tags to all RCS files of a
project but it certainly doesn't copy the files "to a second directory"
and anyone whoever worked with a CVS repository can be expected to now
that. Considering that this means the time necessary for creating a
branch is proportional to the number of files, this is a very slow
operation.

O(1) branching didn't fell from the sky because only Linus Torvalds
looked hard enough for it but was introduced with Subversion which
- when branching - "creates a new directory entry that points to an
existing tree.". J. Random Know-it-all likely just won't notice that
because a branch has to be checked out prior to using it locally for
anything and this (like any other checkout) creates a copy of the files.

The "revolutionary git concept" of "treating the content as a
filesystem" also came from Subversion.

NB: As incomplete list of git commands, this text is probably good
enough and also as introduction to "version control concepts" provides
one keeps in mind that the author doesn't know any SCM but git.