From: Junio C Hamano <gitster@pobox.com>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: Johannes.Schindelin@gmx.de, git@vger.kernel.org
Subject: Re: pd/fetch-jobs, was Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)
Date: Mon, 16 Sep 2019 10:43:28 -0700 [thread overview]
Message-ID: <xmqqh85cb0hr.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <mhng-2c9b8fd0-22e7-4679-9d9b-f8128881fada@palmer-si-x1e> (Palmer Dabbelt's message of "Sat, 14 Sep 2019 06:58:37 -0700 (PDT)")
Palmer Dabbelt <palmer@sifive.com> writes:
> ... It looks
> like there are some test failures when I rebase to the latest master,
> which I'm happy to fix. Just let me know if I should:
> * Send just the first 4 patches, holding onto the last one for later.
> ...
> * Send just a single patch, which wouldn't add the --fetch-jobs and
> --submodule-fetch-jobs arguments.
It is either one of these two, I would say. I am personally much
more comfotable with the usual "backward incompatibility migration"
form (i.e. the former), but apparently I am nto the only person on
the list so ... ;-)
next prev parent reply other threads:[~2019-09-16 17:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 17:26 What's cooking in git.git (Sep 2019, #01; Sat, 7) Junio C Hamano
2019-09-09 18:58 ` Denton Liu
2019-09-09 19:57 ` Junio C Hamano
2019-09-10 0:18 ` Denton Liu
2019-09-09 23:47 ` brian m. carlson
2019-09-10 0:19 ` Junio C Hamano
2019-09-28 23:31 ` Junio C Hamano
2019-09-28 23:35 ` brian m. carlson
2019-09-10 5:04 ` Martin Ågren
2019-09-10 18:23 ` Josh Steadmon
2019-09-11 1:03 ` Matheus Tavares Bernardino
2019-09-11 12:01 ` pd/fetch-jobs, was " Johannes Schindelin
2019-09-12 18:02 ` Junio C Hamano
2019-09-14 13:58 ` Palmer Dabbelt
2019-09-16 17:43 ` Junio C Hamano [this message]
2019-09-16 20:40 ` Palmer Dabbelt
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=xmqqh85cb0hr.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=palmer@sifive.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).