From: "Perry E. Metzger" <perry@piermont.com>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: Good book on Git
Date: Sat, 15 Nov 2014 08:45:58 -0500 [thread overview]
Message-ID: <20141115084558.7bf36715@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <m2k32wsn2t.fsf@fastmail.fm>
On Sat, 15 Nov 2014 14:46:50 +0300 Filipp Gunbin
<fgunbin@fastmail.fm> wrote:
> On 15/11/2014 00:32 +0300, Perry E. Metzger wrote:
>
> > The Git manuals that come with Git itself are of course fully
> > free, but they are not always the easiest introduction.
>
> The git-tutorial pages (1 and 2) provide an easy quickstart help,
> and then usual man pages for various commands are good.
>
Certainly. However, if one is the sort of person who hacks on emacs,
one is also the sort of person who would probably learn quite a bit
about git's model from understanding the underlying infrastructure.
Until I really got how git works, the reason certain things are easy
and certain things are hard, why the tools do what they do, etc., did
not make sense to me.
I think the online book I pointed at does a good job for a
sophisticated user. It also provides a better overview of how
relatively more sophisticated operations with the tools (like
rebasing and such) are best performed.
Perry
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2014-11-15 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 17:56 Good book on Git Perry E. Metzger
2014-11-14 20:53 ` Richard Stallman
2014-11-14 21:32 ` Perry E. Metzger
2014-11-15 11:46 ` Filipp Gunbin
2014-11-15 13:45 ` Perry E. Metzger [this message]
2014-11-15 14:26 ` Przemysław Wojnowski
2014-11-15 16:17 ` Richard Stallman
2014-11-15 18:38 ` Perry E. Metzger
2014-11-16 3:43 ` Richard Stallman
2014-11-16 7:27 ` Tassilo Horn
2014-11-16 7:59 ` Werner LEMBERG
2014-11-16 8:10 ` Tassilo Horn
2014-11-16 19:00 ` Richard Stallman
2014-11-16 18:00 ` Alan Mackenzie
2014-11-16 23:33 ` Gregor Zattler
2014-11-17 2:54 ` Perry E. Metzger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141115084558.7bf36715@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=emacs-devel@gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).