From: Dmitry Potapov <dpotapov@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: What are branches?
Date: Tue, 21 Apr 2009 00:16:06 +0400 [thread overview]
Message-ID: <20090420201606.GH25059@dpotapov.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0904202117010.6771@intel-tinevez-2-302>
On Mon, Apr 20, 2009 at 09:19:10PM +0200, Johannes Schindelin wrote:
>
> The purpose of my message was to make Git old-timers _aware_ of the
> problems newbies have with our notion of branches. And a wish to come up
> with less confusing documentation.
Thank you for your attempt bringing attention to this problem, but I
think anyone who remember their first steps with Git or have observed
other people starting to use Git recently have noticed that already.
I will try quickly summarize my view of it:
- branches in Git are not fundamentally different than in other VCSes,
and clearly correspond commonly used definition of this term.
Obviously, every VCS has some difference in the way how it manages
branches (which makes use of branches in some VCS much easier than in
others).
- obviously, all newcomers have some ideas about branches based on their
previous experience (whether it was another VCS or some books), but
often they do not give much thought to branches before, because they
rarely used them except two or three branches (like maint and master),
and many have never merged branches.
- the graph shown by gitk may be very confusing for beginners, because
they cannot see the branch line, in particular, of the master branch.
- I don't find documentation to be confusing, but it doesn't mean that it
cannot be improved. Yet, based on my observation, most confusion are
among those users who has shown less propensity to read documentation.
Dmitry
next prev parent reply other threads:[~2009-04-20 20:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 15:17 What are branches? Johannes Schindelin
2009-04-19 15:24 ` Michael Witten
2009-04-19 22:10 ` Tuncer Ayaz
2009-04-19 22:29 ` Johannes Schindelin
2009-04-19 22:34 ` Tuncer Ayaz
2009-04-20 11:32 ` Dmitry Potapov
2009-04-20 12:07 ` Michael J Gruber
2009-04-20 13:24 ` Dmitry Potapov
2009-04-20 13:52 ` Michael J Gruber
[not found] ` <200904201614.07735.fge@one2team.com>
2009-04-20 14:27 ` Michael J Gruber
2009-04-20 18:40 ` Dmitry Potapov
2009-04-20 20:58 ` Junio C Hamano
2009-04-20 22:08 ` Marius Vollmer
2009-04-21 0:53 ` Junio C Hamano
2009-04-21 11:41 ` Dmitry Potapov
2009-04-20 14:25 ` Johannes Schindelin
2009-04-20 16:06 ` Björn Steinbrink
2009-04-20 18:59 ` Jakub Narebski
2009-04-20 20:23 ` Björn Steinbrink
2009-04-24 13:08 ` Jakub Narebski
2009-04-24 16:29 ` Björn Steinbrink
2009-04-20 18:47 ` Dmitry Potapov
2009-04-20 19:19 ` Johannes Schindelin
2009-04-20 19:24 ` Michał Kiedrowicz
2009-04-20 20:16 ` Dmitry Potapov [this message]
2009-04-20 21:04 ` Björn Steinbrink
2009-04-20 16:13 ` Brian Gernhardt
2009-04-25 11:11 ` Felipe Contreras
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=20090420201606.GH25059@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.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.
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).