[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Obscure error/warning/information message from git pull

From: Sergey Organov
Subject: Re: Obscure error/warning/information message from git pull
Date: Tue, 18 Nov 2014 23:57:34 +0300
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> It's the latter that I've tried to help to achieve. Sorry if I
>> failed.
> You cannot help people understand new tools if you start by telling
> them to forget everything they've learned.  You should instead build
> on what they know, or think they know, gradually replacing that with
> new knowledge.

Sorry, but I really think that to better understand Git, one should
forget, at least temporarily, some things she learned from other VCSes.
Then after she gets what, say, "branch" means to Git, she can tweak her
previous knowledge to fit.

> Regardless, the concept of "branch" as a separate line of development
> is not killed by Git.  It's just that a branch can be named by its
> tip, and vice versa.
>> My point is that branch name doesn't represent anything else but
>> particular reference to particular commit in Git.
> No, it also represents all the previous commits made on that branch
> that are reachable through first-parents.

Well, given the following history (time goes from left to right):

             - C - D <- foo
... - A - B
             - E - F <- bar

what branch commit A was made on, 'foo' or 'bar'?

You see, you should have had no "made on that branch" in your
description, provided you describe Gits' idea of a branch, not your one,
as Git does not remember on what branch commit was made.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]