From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Yates Newsgroups: gmane.emacs.devel Subject: Re: Obscure error/warning/information message from git pull Date: Tue, 18 Nov 2014 16:59:58 -0500 Message-ID: References: <20141114120604.GA3859@acm.acm> <87389mkjwo.fsf@thinkpad-t440p.tsdh.org> <20141114141434.GM3565@embecosm.com> <20141114180521.GA3168@acm.acm> <20141114230235.GF3168@acm.acm> <20141117141123.GA4294@acm.acm> <83lhn89zxn.fsf@gnu.org> <83bno49xtw.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0117651d5bee16050829375d X-Trace: ger.gmane.org 1416348019 28268 80.91.229.3 (18 Nov 2014 22:00:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Nov 2014 22:00:19 +0000 (UTC) Cc: Sergey Organov , Emacs developers To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 18 23:00:10 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xqqoj-0005Qt-UW for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 23:00:10 +0100 Original-Received: from localhost ([::1]:55602 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqqoj-000763-Mf for ged-emacs-devel@m.gmane.org; Tue, 18 Nov 2014 17:00:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48402) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xqqoc-00074R-5a for emacs-devel@gnu.org; Tue, 18 Nov 2014 17:00:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xqqoa-0006zp-W0 for emacs-devel@gnu.org; Tue, 18 Nov 2014 17:00:01 -0500 Original-Received: from mail-yk0-x22d.google.com ([2607:f8b0:4002:c07::22d]:35820) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqqoZ-0006zb-IX; Tue, 18 Nov 2014 16:59:59 -0500 Original-Received: by mail-yk0-f173.google.com with SMTP id 19so4785099ykq.4 for ; Tue, 18 Nov 2014 13:59:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OEqtA7KZluZBqwciOjVu0+eVAaYIjHO4hsxRW8XBheE=; b=A5eTHS1cEWsfbdOOnhbrT2SdblMea7rdrgI187ow8GeNbnJSjNiY8ViN5rjYnCRgNn 2Imvzn0H07k9LExSw7OgZbMuJ1v4BUjzxDdvgHKR1qqchvMWG1e/FpyuKNnQ+T9Hdp/o hKl8gFM31HSnkpPCEzS0zka5mIyCnPTuALxlChvlz8t6J+lkqR63TMLAJLZxGXjRTBng +xXHdfwPOZatIfxd7PT8Ak/2f/t1hjZ5zl5KC72BigLLIjAsjU/7YghWKtoxhUSgT9W+ HSSRAFNmUhioKdJziSnHj5wKpmHtGg6tQ15lUU4TpwyvSC8KiaeQ56sYMEQwHEbelQvh yHVw== X-Received: by 10.236.14.102 with SMTP id c66mr34106777yhc.23.1416347999004; Tue, 18 Nov 2014 13:59:59 -0800 (PST) Original-Received: by 10.170.200.3 with HTTP; Tue, 18 Nov 2014 13:59:58 -0800 (PST) In-Reply-To: <83bno49xtw.fsf@gnu.org> X-Google-Sender-Auth: D4PAMUx3trbj9rNlaNgKyCemruk X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4002:c07::22d X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177676 Archived-At: --089e0117651d5bee16050829375d Content-Type: text/plain; charset=UTF-8 On Tue, Nov 18, 2014 at 1:18 PM, Eli Zaretskii wrote: > 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. > Earlier VCS often had more reified branches. A phrase that crops up a lot in git descriptions is "lightweight branching". This was achieved by paring back the branch concept - leaving nothing more than the nodes reachable from a named ref - and by making ref manipulation very common. When contrasting git to earlier VCS in none of the git intros I have read have I seen that particular point made. I have been programming for well over 40 years and have used many VCS. Personally I always found branching a hurdle in earlier VCS, something I avoided. After using git for less than a year I can say emphatically that I am far happier and more confident working with git's notion of lightweight branching than with branching in any previous VCS I used (and I have used a _lot_!) I have noticed that as I now use branches actively (both privately and with colleagues) I have a better, deeper understanding of their concepts and mechanics. The fact that a single set of concepts and mechanism scales from the tiny/personal to the large/project-wide helps one polish one's skills. /john --089e0117651d5bee16050829375d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tue, Nov 18, 2014 at 1:18 PM, Eli Zaretskii <eliz@gnu.o= rg> wrote:
You cannot help pe= ople understand new tools if you start by telling
them to forget everything they've learned.=C2=A0 You should instead bui= ld
on what they know, or think they know, gradually replacing that with
new knowledge.

<= /font>
Earlier VCS often had more reifie= d branches. =C2=A0A phrase tha= t crops up a
lot in = git descriptions is "lightweight branching".=C2=A0 This was achie= ved
by paring back t= he branch concept - leaving nothing more than the nodes
reachable from a named ref - and by mak= ing ref manipulation very common.

When contrasting git to earlier=C2=A0VCS in none of the g= it intros I have
read=C2=A0have I seen that particular point ma= de.

I have been programming for wel= l over 40 years and have used many VCS.
Personally I always found branching a hurdle in earlier= VCS, something
I av= oided.=C2=A0 After using git for less than a year I can say emphatically
that I am far happier = and more confident working with git's notion of
lightweight branching than with branching i= n any previous VCS I used
(and=C2=A0I have used=C2= =A0a _lot_!) =C2=A0I have noti= ced that as I now use branches
actively (both privately and with colleagues) I have a better, d= eeper
understanding = of their concepts and mechanics.=C2=A0 The fact that a single
<= div>set of concepts and mechanism sca= les from the tiny/personal to the
large/project-wide=C2=A0helps one polish one's skills.

/john
=


--089e0117651d5bee16050829375d--