From: Han-Wen Nienhuys <hanwen@google.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Taylor Blau" <me@ttaylorr.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Derrick Stolee" <stolee@gmail.com>,
"Josh Steadmon" <steadmon@google.com>,
"Clemens Fruhwirth" <clemens@endorphin.org>
Subject: Re: What's cooking in git.git (Aug 2021, #09; Sun, 29)
Date: Mon, 30 Aug 2021 14:23:20 +0200 [thread overview]
Message-ID: <CAFQ2z_PCUr3D0H-fzfHcFFayzdDJc64=JgVM5_2kuLJn-G9awA@mail.gmail.com> (raw)
In-Reply-To: <87tuj7xhqo.fsf@evledraar.gmail.com>
On Mon, Aug 30, 2021 at 2:03 PM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> Han-Wen: It would be really nice to have this re-rolled sooner than
> later, my and Junio's "fixup" commits at the end are a band-aid, but I
> already ran into wanting to bisect something between master..seen that
> was unnecessarily painful due to the series now not compiling without
> the "fixup" commits at the end.
I am folding in the __FUNCTION__ fix.
However, I thought patches should be sent against the master branch
and not against some intermediate version of 'seen' ?
--
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--
Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
next prev parent reply other threads:[~2021-08-30 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 1:19 What's cooking in git.git (Aug 2021, #09; Sun, 29) Junio C Hamano
2021-08-30 11:00 ` Ævar Arnfjörð Bjarmason
2021-08-30 12:23 ` Han-Wen Nienhuys [this message]
2021-08-30 13:27 ` Ævar Arnfjörð Bjarmason
2021-08-30 13:58 ` Han-Wen Nienhuys
2021-08-30 23:44 ` Junio C Hamano
2021-08-31 3:39 ` Junio C Hamano
2021-09-01 5:04 ` SZEDER Gábor
2021-08-30 14:02 ` Derrick Stolee
2021-08-31 0:29 ` Junio C Hamano
2021-08-31 22:02 ` Jonathan Tan
2021-09-01 14:55 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFQ2z_PCUr3D0H-fzfHcFFayzdDJc64=JgVM5_2kuLJn-G9awA@mail.gmail.com' \
--to=hanwen@google.com \
--cc=avarab@gmail.com \
--cc=clemens@endorphin.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=steadmon@google.com \
--cc=stolee@gmail.com \
--cc=szeder.dev@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).