From: Felipe Contreras <felipe.contreras@gmail.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: [PATCH] Use fast-forward
Date: Sat, 24 Oct 2009 17:17:47 +0300 [thread overview]
Message-ID: <94a0d4530910240717i7c8fe973w2623d095daf04ca6@mail.gmail.com> (raw)
In-Reply-To: <20091024220709.6117@nanako3.lavabit.com>
On Sat, Oct 24, 2009 at 4:07 PM, Nanako Shiraishi <nanako3@lavabit.com> wrote:
> Quoting Felipe Contreras <felipe.contreras@gmail.com>
>
>> As suggested in the mailing list, now I've replaced all instances of 'fast
>> forward' with 'fast-forward'.
>
> I had an impression that the consensus from the previous
> discussion was that there is no such consensus that this
> is an improvement, because there isn't a clear-cut rule?
I don't think anyone wants to preserve the current inconsistent use,
and I haven't seen arguments in favor of 'fast forward' either. My
understanding was that the comments were in favor of 'fast-forward'
but making it consistent across the code-base:
http://marc.info/?l=git&m=125532404330701&w=2
http://marc.info/?l=git&m=125535210203730&w=2
--
Felipe Contreras
prev parent reply other threads:[~2009-10-24 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 8:31 [PATCH] Use fast-forward Felipe Contreras
2009-10-24 8:31 ` [PATCH] Use 'fast-forward' all over the place Felipe Contreras
2009-10-24 17:50 ` Junio C Hamano
2009-10-24 19:12 ` Felipe Contreras
2009-10-24 19:44 ` Junio C Hamano
2009-10-25 8:56 ` Felipe Contreras
2009-10-25 3:41 ` Junio C Hamano
2009-10-25 7:15 ` Junio C Hamano
2009-10-25 7:19 ` Junio C Hamano
2009-10-25 7:22 ` Junio C Hamano
2009-10-25 9:06 ` Felipe Contreras
2009-10-25 9:02 ` Felipe Contreras
2009-10-24 13:07 ` [PATCH] Use fast-forward Nanako Shiraishi
2009-10-24 14:17 ` Felipe Contreras [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=94a0d4530910240717i7c8fe973w2623d095daf04ca6@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nanako3@lavabit.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).