From: David Greaves <david@dgreaves.com>
To: dwheeler@dwheeler.com
Cc: Petr Baudis <pasky@ucw.cz>,
Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org
Subject: Re: Change "pull" to _only_ download, and "git update"=pull+merge?
Date: Tue, 19 Apr 2005 10:18:55 +0100 [thread overview]
Message-ID: <4264CCFF.30400@dgreaves.com> (raw)
In-Reply-To: <42646967.9030903@dwheeler.com>
David A. Wheeler wrote:
> I propose changing "pull" to ONLY download, and "update" to pull AND merge.
> Why? It seems oddly inconsistent that "pull" sometimes merges
> in changes, but at other times it doesn't.
true
> I propose that there be two subcommands, "pull" and "update"
> (now that "update" isn't a reserved word again).
> A "git pull" ONLY downloads; a "git update" pulls AND merges.
What's the most common thing to do? pull or update?
which is easier to type?
what are people used to?
I'm not sure but I suggest that pull and get would be better choices.
git pull
git get
is it rare enough to justify:
git --download-only pull
David
--
next prev parent reply other threads:[~2005-04-19 9:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 1:56 [PATCH] Add "clone" support to lntree Daniel Barkalow
2005-04-16 2:47 ` Petr Baudis
2005-04-16 2:58 ` Petr Baudis
2005-04-16 3:16 ` Linus Torvalds
2005-04-16 11:39 ` Petr Baudis
2005-04-16 3:17 ` Daniel Barkalow
2005-04-16 23:33 ` Petr Baudis
2005-04-17 0:07 ` Daniel Barkalow
2005-04-19 1:12 ` Petr Baudis
2005-04-19 2:13 ` Change "pull" to _only_ download, and "git update"=pull+merge? David A. Wheeler
2005-04-19 9:18 ` David Greaves [this message]
2005-04-19 9:28 ` Petr Baudis
2005-04-19 10:05 ` Martin Schlemmer
2005-04-19 10:50 ` Petr Baudis
2005-04-19 13:54 ` Jon Seymour
2005-04-19 14:40 ` Martin Schlemmer
2005-04-19 18:28 ` Daniel Barkalow
2005-04-19 22:39 ` David A. Wheeler
2005-04-19 23:20 ` Daniel Barkalow
2005-04-20 7:01 ` Ingo Molnar
2005-04-20 20:05 ` Petr Baudis
2005-04-20 20:32 ` Ingo Molnar
2005-04-20 21:15 ` Petr Baudis
2005-04-20 23:58 ` David Mansfield
2005-04-20 20:45 ` Ingo Molnar
2005-04-16 3:06 ` Add "clone" support to lntree Daniel Barkalow
2005-04-16 23:00 ` Petr Baudis
2005-04-16 23:07 ` Daniel Barkalow
2005-04-16 23:44 ` Petr Baudis
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=4264CCFF.30400@dgreaves.com \
--to=david@dgreaves.com \
--cc=barkalow@iabervon.org \
--cc=dwheeler@dwheeler.com \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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.