From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: 乙酸鋰 <ch3cooli@gmail.com>, git@vger.kernel.org
Subject: Re: git pull --no-ff documentation
Date: Mon, 01 Oct 2012 13:24:40 -0700 [thread overview]
Message-ID: <7vmx06aqk7.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7EAC0E5241D6431599764E90FA821FCF@PhilipOakley> (Philip Oakley's message of "Mon, 1 Oct 2012 20:54:59 +0100")
"Philip Oakley" <philipoakley@iee.org> writes:
>> This actually is not about --no-ff but about --no-tags. Any option
>> that "pull" itself does not care about stops the command line parser
>> and the remainder of the command line is fed to underlying "fetch".
>>
>
> Should this be said within the documentation's synopsis ?
>
> e.g.
> git pull [pull_options] [merge_options] [fetch_options [<repository>
> [<refspec>…]]
We certainly could do that, but I was hoping somebody would
volunteer to make it easier to the end users so that they do not
have to remember which one is which.
The "perhaps something like this?" patch was a hint to show the
first step in that preferrable direction.
prev parent reply other threads:[~2012-10-01 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 3:36 git pull --no-ff documentation 乙酸鋰
2012-10-01 4:42 ` Junio C Hamano
2012-10-01 19:54 ` Philip Oakley
2012-10-01 20:24 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vmx06aqk7.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=ch3cooli@gmail.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).