From: "Philip Oakley" <philipoakley@iee.org>
To: "Marc Branchaud" <marcnarc@xiplink.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Pull is Mostly Evil
Date: Fri, 2 May 2014 23:12:52 +0100 [thread overview]
Message-ID: <B2C7522180DD4894BB18B91CAFD35FF9@PhilipOakley> (raw)
In-Reply-To: 5363BB9F.40102@xiplink.com
From: "Marc Branchaud" <marcnarc@xiplink.com>
Sent: Friday, May 02, 2014 4:37 PM
> (Apologies for not CCing all the folks who've participated in the
> "Pull is
> Evil" thread -- I couldn't find a good branch of that thread for this
> message.)
>
> OK, so maybe "git pull" is just Mostly Evil. People seem to have
> found many
> different ways to make it work for them.
>
> But in reality "git pull" has become a chimera that confuses a large
> number
> of new users, and that experienced users either avoid entirely or
> customize
> to give them a convenient shorthand for working in their particular
> environment. As a tool for new git users, it just doesn't seem to be
> achieving its goals.
>
> I think the git project as a whole would benefit if it started to
> treat "git
> pull" as an advanced command, in the sense that it needs to be
> configured by
> an experienced user in order to make it correctly follow a project's
> workflow. Once it's configured properly, "git pull" is a powerful
> tool that
> gives users an easy way to do complex things. In that sense, it may
> be
> appropriate for a project to tailor "git pull" as it likes, then teach
> its
> own users to use the command.
>
> However, when it comes to teaching people how to use git qua git, "git
> pull"
> should be the last thing they learn about, because it's only after you
> understand various basic git concepts that you can configure "git
> pull" to do
> the right thing.
>
> To that end, I suggest that pull's default behaviour should be to do
> *nothing*. It should just print out a message to the effect that it
> hasn't
> been configured, and that the user should run "git help pull" for
> guidance.
>
I tend to agree.
The hard part is making sure folk have enough prior learning to make a
choice that their will fit their real needs.
> It'll take quite a bit of time, but I think that if we change our
> attitude
> towards "git pull" and take this unconfigured-by-default approach,
> then in a
> few years the entire git ecosystem will be in a better place.
>
> M.
> --
Philip
next prev parent reply other threads:[~2014-05-02 22:12 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 15:37 Pull is Mostly Evil Marc Branchaud
2014-05-02 15:45 ` David Kastrup
2014-05-02 16:05 ` Philip Oakley
2014-05-02 19:05 ` Felipe Contreras
2014-05-02 22:34 ` Philip Oakley
2014-05-02 22:53 ` Jonathan Nieder
2014-05-03 20:24 ` Philip Oakley
2014-05-02 23:23 ` Felipe Contreras
2014-05-03 11:24 ` Philip Oakley
2014-05-03 11:30 ` Felipe Contreras
2014-05-02 19:31 ` David Lang
2014-05-02 19:37 ` David Kastrup
2014-05-02 18:13 ` Junio C Hamano
2014-05-02 19:11 ` Felipe Contreras
2014-05-02 20:06 ` Junio C Hamano
2014-05-02 20:58 ` Felipe Contreras
2014-05-02 21:48 ` Jeff King
2014-05-02 21:55 ` Felipe Contreras
2014-05-02 22:36 ` Jeff King
2014-05-02 23:27 ` Felipe Contreras
2014-05-03 2:18 ` David Kastrup
2014-05-06 22:06 ` Junio C Hamano
2014-05-06 22:19 ` Felipe Contreras
2014-05-03 7:56 ` Richard Hansen
2014-05-03 8:17 ` David Kastrup
2014-05-03 9:04 ` Felipe Contreras
2014-05-03 9:56 ` David Kastrup
2014-05-04 4:30 ` David Lang
2014-05-04 4:38 ` Felipe Contreras
2014-05-04 6:13 ` David Kastrup
2014-05-04 6:50 ` James Denholm
2014-05-04 7:48 ` David Kastrup
2014-05-04 9:51 ` Felipe Contreras
2014-05-04 10:37 ` James Denholm
2014-05-04 11:02 ` David Kastrup
2014-05-03 9:26 ` Felipe Contreras
2014-05-03 22:09 ` Richard Hansen
2014-05-04 3:08 ` Felipe Contreras
2014-05-04 7:49 ` Richard Hansen
2014-05-04 10:17 ` Felipe Contreras
2014-05-04 19:09 ` Richard Hansen
2014-05-04 21:13 ` Felipe Contreras
2014-05-05 5:44 ` Richard Hansen
2014-05-05 5:47 ` Felipe Contreras
2014-05-07 22:37 ` Max Kirillov
2014-05-03 10:00 ` John Szakmeister
2014-05-05 15:39 ` Richard Hansen
2014-05-05 18:15 ` Felipe Contreras
2014-05-02 22:12 ` Philip Oakley [this message]
2014-05-09 19:49 ` Marc Branchaud
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=B2C7522180DD4894BB18B91CAFD35FF9@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.com \
/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).