git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Chris Riddoch <riddochc@gmail.com>
Cc: Sean <seanlkml@sympatico.ca>,
	Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	git@vger.kernel.org
Subject: Re: [DRAFT] Branching and merging with git
Date: Fri, 17 Nov 2006 23:50:37 +0100	[thread overview]
Message-ID: <20061117225037.GI7201@pasky.or.cz> (raw)
In-Reply-To: <6efbd9b70611171436t1e0cadf2j7e9387ca77f85538@mail.gmail.com>

On Fri, Nov 17, 2006 at 11:36:25PM CET, Chris Riddoch wrote:
> On 11/17/06, Petr Baudis <pasky@suse.cz> wrote:
> >If someone writes a crash course in pure Git covering the same grounds
> >as the current ones (possibly by just extending/retouching the tutorial)
> >(it does not necessarily need to be a "refugee" crash course, it can
> >build up from scratch), I can add it on the web. If it becomes as easy
> >to use and with as mild learning curve as Cogito, it means Cogito got
> >mostly obsolete and I'll happily remove the Cogito crash courses from
> >the web.
> 
> As a relatively new user myself, I ran into the same confusion when I
> came to the website for the first time.  One of the most prominent
> things on the front page is the "Git Crash Courses."  Clicking on that
> gives me the crash courses, all of which are about Cogito, not for
> Git.  So why doesn't the front page say "Cogito Crash Courses"
> instead?
> 
> And I don't think it matters much whether Cogito makes things easier
> or not -- the Git website really should make Git's documentation more
> prominent than Cogito's.  I'd expect the opposite of Cogito's website.

I think the difference here is the Git _tool_ vs. the Git version
control system. Cogito is an element of the second: To use Git, you can
either use the Git tool or the Cogito tool or the StGIT tool or even
just the qgit tool (which also lets you inspect the working copy and
commit). I believe the tool best suited for general usage by newbies _at
this point_ is Cogito, so that's what I use for introduction to Git. I'm
not saying this is ideal situation and I and others are/will be working
to fix it.

I'm all for making it more obvious what's going on at the website, I
think the current wording is better. Also, if people believe that a
crash course for core Git would help things, I'm all for it as well.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1

  reply	other threads:[~2006-11-17 22:50 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 22:17 [DRAFT] Branching and merging with git linux
2006-11-16 23:47 ` Junio C Hamano
2006-11-17  1:13   ` linux
2006-11-17  1:31     ` Junio C Hamano
2006-11-17  1:09 ` Junio C Hamano
2006-11-17  3:17   ` linux
2006-11-17  5:55     ` Junio C Hamano
2006-11-17  9:37 ` Jakub Narebski
2006-11-17  9:41 ` Jakub Narebski
2006-11-17 10:37 ` Jakub Narebski
2006-11-17 15:32 ` Theodore Tso
2006-11-17 15:57   ` Sean
2006-11-17 16:19     ` Nguyen Thai Ngoc Duy
2006-11-17 16:25       ` Marko Macek
2006-11-17 16:33         ` Petr Baudis
2006-11-17 16:34       ` Sean
     [not found]       ` <20061117113404.810fd4ea.seanlkml@sympatico.ca>
2006-11-17 16:53         ` Petr Baudis
2006-11-17 17:01           ` Sean
     [not found]           ` <20061117120154.3eaf5611.seanlkml@sympatico.ca>
2006-11-17 21:31             ` Petr Baudis
2006-11-17 22:36               ` Chris Riddoch
2006-11-17 22:50                 ` Petr Baudis [this message]
2006-11-17 23:30               ` Sean
2006-11-17 18:21   ` J. Bruce Fields
2006-11-18  0:13     ` linux
2006-11-18  0:32       ` Jakub Narebski
2006-11-18  0:40       ` Junio C Hamano
2006-11-18  1:11         ` Junio C Hamano
2006-11-20 23:51           ` [DRAFT 2] " linux
2006-11-22 11:02             ` [Patch to DRAFT 2 (1/2)] " Junio C Hamano
2006-11-22 11:02             ` [Patch to DRAFT 2 (2/2)] " Junio C Hamano
2006-11-22 13:36               ` Rene Scharfe
2006-12-04  1:19             ` [DRAFT 2] " J. Bruce Fields
2006-12-04  7:23               ` J. Bruce Fields
2006-12-04 10:56                 ` Johannes Schindelin
2006-12-15 21:38             ` Jakub Narebski
2006-12-15 21:41               ` J. Bruce Fields
2006-11-22 11:51           ` [DRAFT] " Junio C Hamano
2006-11-19 17:50     ` J. Bruce Fields
2006-11-19 17:59       ` Git manuals Petr Baudis
2006-11-19 18:16         ` Jakub Narebski
2006-11-19 19:50           ` Robin Rosenberg
2006-11-19 19:36         ` J. Bruce Fields
2006-11-26  4:01       ` [PATCH] Documentation: add a "git user's manual" J. Bruce Fields
2006-11-17 17:44 ` [DRAFT] Branching and merging with git J. Bruce Fields
2006-11-17 18:16   ` Jakub Narebski
2007-01-03 17:04 ` Theodore Tso
2007-01-03 17:08   ` Junio C Hamano
2007-01-04  5:28     ` linux
2007-01-04  6:11       ` Junio C Hamano
2007-01-07 23:44   ` J. Bruce Fields
2007-01-08  0:24     ` Junio C Hamano
2007-01-08  2:35       ` J. Bruce Fields
2007-01-08 13:04         ` David Kågedal
2007-01-08 14:03         ` Theodore Tso
2007-01-09  2:41           ` J. Bruce Fields
2007-01-09  8:46             ` Andreas Ericsson
2007-01-09 15:49               ` J. Bruce Fields
2007-01-09 16:58               ` Theodore Tso
2007-01-10  4:15                 ` J. Bruce Fields
2007-01-08  0:40     ` Theodore Tso
2007-01-08  0:46       ` J. Bruce Fields
2007-01-08  1:22         ` Jakub Narebski
2007-01-08  1:46         ` Horst H. von Brand
2007-01-08  2:22           ` J. Bruce Fields
2007-01-08 12:38         ` Guilhem Bonnefille
2007-01-09  4:17           ` J. Bruce Fields

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=20061117225037.GI7201@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=riddochc@gmail.com \
    --cc=seanlkml@sympatico.ca \
    /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).