From: "Jonas Juselius" <jonas.juselius@chem.uit.no>
To: "Benoit Sigoure" <tsuna@lrde.epita.fr>
Cc: "git" <git@vger.kernel.org>
Subject: Re: Git in a Nutshell guide
Date: Tue, 20 Nov 2007 12:34:38 +0100 [thread overview]
Message-ID: <1195558478.10369.8.camel@localhost> (raw)
In-Reply-To: <3057F6F3-BEAA-447A-AB79-A0AFB7DB8826@lrde.epita.fr>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
On Mon, 2007-11-19 at 17:49 +0100, Benoit Sigoure wrote:
> You can create a repository on repo.or.cz then :)
I will :=)
>
> As it is often the case different people happen to work on similar
> things without knowing each other. I started http://repo.or.cz/w/
> tutorial.git which is meant to be a big Beamer presentation that
> presents Git thoroughly. I wrote some ideas but didn't start to
> write the slides. Just in case you want to have a look.
Thanks, there are certainly some things in that document that I ought to
consider incorporating in the guide. But for now I'll let it rest for a
little while, because I don't have time to mess with it. Patches are
always welcome ;)
> One of the things you said in your guide is that Git is easy to
> learn. I think this is wrong. Git is way more complicated than most
> other SCMs, especially compared to SVN. Its documentation is far
> behind, compared to what other SCMs have. There is no real user
> guide and the man pages are incomplete, at best. I know saying this
> is a bit harsh, especially to the people out there that are working
> and sending patches to improve the documentation, but I think we have
> to admit that it's true, even though Git is making progress on this
> aspect.
Well, you are right to some extent. But it's this gap I would like to
fill with the nutshell guide. The "for normal people" slogan is meant to
refer to non-technical developers (like scientists). I should probably
include a little section in the intro describing distributed vs.
centralised SCMs in general.
Thanks for the input,
.jonas.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-20 11:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 13:05 Git in a Nutshell guide Jonas Juselius
2007-11-19 13:29 ` Jakub Narebski
2007-11-19 14:33 ` Jonas Juselius
2007-11-22 8:22 ` David Kågedal
2007-11-23 9:28 ` Jakub Narebski
2007-11-19 15:02 ` Brian Downing
2007-11-19 15:03 ` Brian Downing
2007-11-19 15:48 ` Nicolas Pitre
2007-11-19 16:05 ` Jakub Narebski
2007-11-19 16:14 ` Jonas Juselius
2007-11-19 16:49 ` Benoit Sigoure
2007-11-19 22:01 ` Daniel Barkalow
2007-11-20 11:34 ` Jonas Juselius [this message]
2007-11-20 23:57 ` Jakub Narebski
2007-11-21 19:45 ` Jan Hudec
2007-11-21 21:32 ` Jakub Narebski
2007-11-22 16:37 ` jhud7196
2007-11-22 13:15 ` Jonas Juselius
2007-11-22 14:19 ` Jonathan del Strother
2007-11-22 14:24 ` Johannes Schindelin
2007-11-22 16:57 ` jhud7196
2007-11-19 16:45 ` Lars Hjemli
2007-11-19 16:56 ` Jonas Juselius
2007-11-19 16:57 ` Benoit Sigoure
2007-11-19 17:04 ` Lars Hjemli
2007-11-19 18:10 ` Benoit Sigoure
2007-11-19 18:13 ` J. Bruce Fields
2007-11-19 18:13 ` Matthieu Moy
2007-11-19 18:35 ` [PATCH] Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys Matthieu Moy
2007-11-19 20:13 ` Junio C Hamano
2007-11-19 20:28 ` Matthieu Moy
2007-11-19 20:31 ` Matthieu Moy
2007-11-19 21:15 ` Git in a Nutshell guide Benoit Sigoure
2007-11-19 21:33 ` Matthieu Moy
2007-11-19 21:51 ` Benoit Sigoure
2007-11-19 22:23 ` J. Bruce Fields
2007-11-19 22:29 ` Junio C Hamano
2007-11-19 22:59 ` Matthieu Moy
2007-11-19 23:07 ` Junio C Hamano
2007-11-19 17:05 ` Matthieu Moy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1195558478.10369.8.camel@localhost \
--to=jonas.juselius@chem.uit.no \
--cc=git@vger.kernel.org \
--cc=tsuna@lrde.epita.fr \
/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.
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 NNTP newsgroup(s).