Re: [PATCH] man: git pull -r is a short for --rebase
- From
Miklos Vajna <vmiklos@suse.cz>
- Date
- Aug 17, 2012, 05:38 UTC
- Message-ID
- <20120817053826.GB22313@suse.cz>
- In-Reply-To
- <7vzk5uzgqa.fsf@alter.siamese.dyndns.org>
On Thu, Aug 16, 2012 at 02:09:33PM -0700, Junio C Hamano <gitster@pobox.com> wrote:
Show 6 quoted lines
> The reason I do not think "pull -r" gives much value to the users to > trigger "pull --rebase" is because the use of "pull --rebase" is > very project specific. If you are working on a project that forbids > merges, you would _always_ want to run "pull --rebase", which means > you would likely have it configured and would not be typing from the > command line.
I agree that it's a bit strange, but based on a quick search, it seems multiple projects already advertise git pull -r (i.e. not --rebase and not a configuration option):
http://lilypond.org/doc/v2.15/Documentation/contributor/pulling-and-rebasing http://wiki.documentfoundation.org/Git_For_LibreOffice_Developers http://www.wiremod.com/forum/wiremod-general-chat/29517-git-introduction-incomplete-unformatted.html
So it seems making -r refer to --recurse-submodules would already cause quite some pain to users.