Discussion:
Any Git power users here?
(too old to reply)
Martin Gregorie
2020-04-12 00:30:19 UTC
Permalink
I'm having to pick up Git in a hurry but, as a long-time CVS user
(started using it in the late 80s) I'm having trouble understanding its
design philosophy and how to use it in non-trivial situations.

I have a copy of the "Git pocket guide" but its turned out to be a recipe
book: good if you want to do what it has recipes for, but of very
marginal use for anything else and with remarkably little to say about
key management. In short, itd of more use as a firelighter than a guide
to the care and feeding of Git.

So, can anybody recommend a decent Git book?

A fairly quick search in the depths of Amazon suggests that "Professional
Git" by Brent Laster, pub Wrox may fit the bill. So, any comments about
it would be appreciated too.
--
Martin | martin at
Gregorie | gregorie dot org
Les Cargill
2020-04-15 07:40:03 UTC
Permalink
Post by Martin Gregorie
I'm having to pick up Git in a hurry but, as a long-time CVS user
(started using it in the late 80s) I'm having trouble understanding its
design philosophy and how to use it in non-trivial situations.
I have a copy of the "Git pocket guide" but its turned out to be a recipe
book: good if you want to do what it has recipes for, but of very
marginal use for anything else and with remarkably little to say about
key management. In short, itd of more use as a firelighter than a guide
to the care and feeding of Git.
So, can anybody recommend a decent Git book?
A fairly quick search in the depths of Amazon suggests that "Professional
Git" by Brent Laster, pub Wrox may fit the bill. So, any comments about
it would be appreciated too.
I'm a low-power user.

You have to establish a repo. That's "git init --bare <directory>". You
want this to be empty ( it's in a shared space ).

"git clone <directory> <target>" from the repo you created into a new
directory ( that doesn't exist ) in your local space. Copy over the
files you want to be in the repo in to the new directory. "git add
<file>" ( repeat ) , then
"git commit", then "git push".

I always "git" something wrong, but that's the basic lifecycle.

It'll do branching and what not. Another chapter perhaps ( I haven't hit
that very hard ).

https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell
https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging
--
Les Cargill
Joachim Ott
2020-05-16 21:57:46 UTC
Permalink
I like this link as simple basic introduction:

https://rogerdudler.github.io/git-guide/index.html

Loading...