git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Hvammen Johansen" <hvammen@gmail.com>
To: "Ping Yin" <pkufranky@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 2/5] Introduce -ff=<fast forward option>
Date: Sat, 3 May 2008 15:04:08 -0700	[thread overview]
Message-ID: <402c10cd0805031504t276e95ffx662004a25c85957f@mail.gmail.com> (raw)
In-Reply-To: <46dff0320805020533u179e16cej2c4db3105252d0bd@mail.gmail.com>

On Fri, May 2, 2008 at 5:33 AM, Ping Yin <pkufranky@gmail.com> wrote:
>  only and never are both adverb,but allow is a verb. So how about using
>  auto instead of allow?

I don;t intend to change this this late.  I think we are fine with the
current names.

-- 
Sverre Hvammen Johansen

      reply	other threads:[~2008-05-03 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24  5:46 [PATCH 2/5] Introduce -ff=<fast forward option> Sverre Hvammen Johansen
2008-05-02 12:33 ` Ping Yin
2008-05-03 22:04   ` Sverre Hvammen Johansen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=402c10cd0805031504t276e95ffx662004a25c85957f@mail.gmail.com \
    --to=hvammen@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pkufranky@gmail.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).