git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: [PATCH] Use 'fast-forward' all over the place
Date: Sun, 25 Oct 2009 12:02:27 +0300	[thread overview]
Message-ID: <94a0d4530910250202h7a890575md080a554f9e0b3e6@mail.gmail.com> (raw)
In-Reply-To: <7v1vks2l8q.fsf@alter.siamese.dyndns.org>

On Sun, Oct 25, 2009 at 6:41 AM, Junio C Hamano <gitster@pobox.com> wrote:
> This is the latter half of my review; please see
>
>    From:       Junio C Hamano <gitster@pobox.com>
>    Subject: Re: [PATCH] Use 'fast-forward' all over the place
>    Date:       Sat, 24 Oct 2009 10:50:05 -0700
>    Message-ID: <7v3a587kc2.fsf@alter.siamese.dyndns.org>
>
> for the other half.
>
> Felipe Contreras <felipe.contreras@gmail.com> writes:

>> diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
>> @@ -315,8 +315,8 @@ generate_update_branch_email()
>>       # "remotes/" will be ignored as well.
>>
>>       # List all of the revisions that were removed by this update, in a
>> -     # fast forward update, this list will be empty, because rev-list O
>> -     # ^N is empty.  For a non fast forward, O ^N is the list of removed
>> +     # fast-forward update, this list will be empty, because rev-list O
>> +     # ^N is empty.  For a non fast-forward, O ^N is the list of removed
>
> Wasn't non-fast-forward a single compound word of three?

Yes, but as I mentioned before; it's not something I'm tackling on
this patch: only "non-fast forward". I think a separate patch should
be done for "non fast.forward" -> non-fast-forward.

>> diff --git a/git-gui/lib/branch_create.tcl b/git-gui/lib/branch_create.tcl
>> index 3817771..f1235c7 100644
>> --- a/git-gui/lib/branch_create.tcl
>> +++ b/git-gui/lib/branch_create.tcl
>> @@ -77,7 +77,7 @@ constructor dialog {} {
>>               -variable @opt_merge
>>       pack $w.options.merge.no -side left
>>       radiobutton $w.options.merge.ff \
>> -             -text [mc "Fast Forward Only"] \
>> +             -text [mc "Fast-forward Only"] \
>>               -value ff \
>>               -variable @opt_merge
>>       pack $w.options.merge.ff -side left
>
> Please leave git-gui out; (1) it is not managed by me and the patch should
> be fed to Shawn separately, and (2) updating [mc] keystrings must need
> matching updates to the translation file and the templates.
>
> I also think this is a label string and the capitalization must be kept,
> i.e. "Fast-Forward Only".

Ok.

>> diff --git a/t/t1001-read-tree-m-2way.sh b/t/t1001-read-tree-m-2way.sh
>> @@ -51,7 +51,7 @@ check_cache_at () {
>>  }
>>
>>  cat >bozbar-old <<\EOF
>> -This is a sample file used in two-way fast forward merge
>> +This is a sample file used in two-way fast-forward merge
>>  tests.  Its second line ends with a magic word bozbar
>>  which will be modified by the merged head to gnusto.
>>  It has some extra lines so that external tools can
>
> Doesn't changing this change the actual test blob used?  Do you know if
> the test still passes when git is not broken?

I didn't check. I will.

Cheers.

-- 
Felipe Contreras

  parent reply	other threads:[~2009-10-25  9:02 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 [this message]
2009-10-24 13:07 ` [PATCH] Use fast-forward Nanako Shiraishi
2009-10-24 14:17   ` Felipe Contreras

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=94a0d4530910250202h7a890575md080a554f9e0b3e6@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).