All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2021, #04; Tue, 10)
Date: Wed, 11 Aug 2021 09:13:23 -0700	[thread overview]
Message-ID: <xmqqr1f09cyk.fsf@gitster.g> (raw)
In-Reply-To: <YROElmCJQGaR8Lsx@carlos-mbp.lan> ("Carlo Marcelo Arenas Belón"'s message of "Wed, 11 Aug 2021 01:04:38 -0700")

Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:

> On Tue, Aug 10, 2021 at 06:12:41PM -0700, Junio C Hamano wrote:
>> 
>> * cb/ci-build-pedantic (2021-08-09) 1 commit
>>  - ci: run a pedantic build as part of the GitHub workflow
>>  (this branch uses cb/many-alternate-optim-fixup.)
>> 
>>  CI update.
>> 
>>  Will merge to 'next'.
>
> this version has the bug you reported[1] and provided a fix for
> because the base image doesn't include git, and while the bug is
> harmless it is still silly enough that should be worth fixing
> before going to next IMHO..

Will mark it as "expecting a reroll".  I do not think we are in a
hurry for this step, even though, as I said, we would probably want
to have the two other changes in the upcoming release.

> I was preparing a version 2 reroll that included the tests, as
> you suggested, which I was also planning to make a little more
> useful by including other test dependencies missing from other jobs.
>
> on that line, I also forgot to build with PCRE, which was the reason
> why it was included as a dependency, and that has been corrected as
> well; alternatively it could be removed and make the job slightly faster.

Sounds good.  We are not in a hurry for anything that may go into
'next' at this stage.  A version that you think will help us start
the cycle after this one well would be desirable.

Thanks.

  reply	other threads:[~2021-08-11 16:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  1:12 What's cooking in git.git (Aug 2021, #04; Tue, 10) Junio C Hamano
2021-08-11  1:34 ` brian m. carlson
2021-08-11  7:22 ` Fabian Stelzer
2021-08-11  8:04 ` Carlo Marcelo Arenas Belón
2021-08-11 16:13   ` Junio C Hamano [this message]
2021-08-11  9:51 ` Phillip Wood
2021-08-11 16:19   ` Junio C Hamano
2021-08-13  8:10     ` ZheNing Hu
2021-08-11 10:45 ` Atharva Raykar
2021-08-11 17:30   ` Junio C Hamano
2021-08-11 12:21 ` Patrick Steinhardt
2021-08-11 16:44   ` Junio C Hamano
2021-08-11 17:49 ` David Turner
2021-08-11 19:00   ` 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=xmqqr1f09cyk.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=carenas@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.