All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2017, #03; Wed, 10)
Date: Wed, 10 May 2017 19:19:54 -0700	[thread overview]
Message-ID: <xmqqvap8ceyd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CACBZZX4VjwXNhFCwhd=-5ArWOvR5E2GDjWZf5dwz3Y4iCS0yYg@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Wed, 10 May 2017 10:12:23 +0200")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> On Wed, May 10, 2017 at 7:18 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> [New Topics]
>>
>> * ab/compat-regex-update (2017-05-09) 2 commits
>>  - compat/regex: update the gawk regex engine from upstream
>>  - compat/regex: add a README with a maintenance guide
>>
>>  Will merge to 'next'.
>
> [Sent last E-Mail too soon]
>
> There's a tiny typo in "compat/regex: update the gawk regex engine
> from upstream", one of the two bullet points says "Git project.f",
> should say "Git project.", i.e. without the stray ".f".

Yeah, I recall seeing it and feeling puzzled when I queued it.  Will
remove and requeue.

Thanks.

> If you don't mind amending that before merging it down that would be
> great, due to the whole multi-patch !fixup -> you needing to squash
> that sounds easier....

  reply	other threads:[~2017-05-11  2:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  5:18 What's cooking in git.git (May 2017, #03; Wed, 10) Junio C Hamano
2017-05-10  8:08 ` Ævar Arnfjörð Bjarmason
2017-05-10  9:04   ` Jean-Noël AVILA
2017-05-11  1:12     ` Junio C Hamano
2017-05-11  2:50   ` Junio C Hamano
2017-05-10  8:12 ` Ævar Arnfjörð Bjarmason
2017-05-11  2:19   ` Junio C Hamano [this message]
2017-05-11 13:08 ` Johannes Schindelin
2017-05-12  5:29   ` Junio C Hamano
2017-05-11 13:09 ` Johannes Schindelin
2017-05-11 16:35   ` Lars Schneider
2017-05-11 21:31 ` Marc Branchaud
2017-05-11 23:38   ` Jeff King
2017-05-12  1:01     ` Junio C Hamano

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=xmqqvap8ceyd.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.