From: "Matthias Urlichs" <matthias@urlichs.de>
To: git@vger.kernel.org
Subject: Re: Git user survey and `git pull`
Date: Fri, 22 Sep 2006 21:05:23 +0000 (UTC) [thread overview]
Message-ID: <ef1j6j$8sn$1@sea.gmane.org> (raw)
In-Reply-To: 20060921162401.GD3934@spearce.org
For what it's worth, I'm in favor of renaming the things.
IMHO, we do not need that kind of baggage. Sure, you explain it once and
people hopefully remember -- except that they don't, not always anyway,
and novice users can't be expected to be notice, let alone repair, that
kind of damage.
*I* make that stupid pull/fetch/merge mistake sometimes,
and I'm not exactly new to git...
On Thu, 21 Sep 2006 12:24:01 -0400, Shawn Pearce wrote:
> Current Shoulda Been
> --------------- ----------------
> git-push git-push
> git-fetch git-pull
> git-pull . foo git-merge foo
> git-pull git-pull --merge
> git-merge git-merge-driver
>
The new programs can (for the most part) recognize when they're called with
"old" semantics, and spit out a warning.
--
Matthias Urlichs
next prev parent reply other threads:[~2006-09-23 6:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 16:24 Git user survey and `git pull` Shawn Pearce
2006-09-21 16:40 ` Petr Baudis
2006-09-21 17:38 ` Linus Torvalds
2006-09-21 18:05 ` Nicolas Pitre
2006-09-22 4:57 ` Junio C Hamano
2006-09-22 10:34 ` Santi
2006-09-22 19:08 ` Junio C Hamano
2006-09-22 23:24 ` Santi
2006-09-21 17:02 ` Nicolas Pitre
2006-09-21 17:09 ` Shawn Pearce
2006-09-21 17:12 ` Johannes Schindelin
2006-09-21 17:17 ` Jakub Narebski
2006-09-22 21:05 ` Matthias Urlichs [this message]
2006-09-23 11:51 ` Alan Chandler
2006-09-23 14:12 ` Johannes Schindelin
2006-09-23 8:54 ` Jakub Narebski
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='ef1j6j$8sn$1@sea.gmane.org' \
--to=matthias@urlichs.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.