From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>, Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2022, #02; Fri, 5)
Date: Wed, 10 Aug 2022 11:26:26 +0200 (CEST) [thread overview]
Message-ID: <o5340r34-027q-4ops-93o1-8368s4qropo5@tzk.qr> (raw)
In-Reply-To: <xmqqa68evodq.fsf@gitster.g>
Hi Junio & Eric,
On Mon, 8 Aug 2022, Junio C Hamano wrote:
> Eric Sunshine <sunshine@sunshineco.com> writes:
>
> > On Fri, Aug 5, 2022 at 11:44 PM Junio C Hamano <gitster@pobox.com> wrote:
> >> * es/doc-creation-factor-fix (2022-07-28) 2 commits
> >> - range-diff: clarify --creation-factor=<factor>
> >> - format-patch: clarify --creation-factor=<factor>
> >>
> >> Expecting a reroll.
> >> source: <7229p500-p2r4-on87-6802-8o90s36rr3s4@tzk.qr>
> >
> > Per [1] and [2], I think the intention was to drop these patches
> > rather than moving forward with them.
> >
> > [1]: https://lore.kernel.org/git/CAPig+cQ94oC-6wftkP_=RSEsOVPKeuBWuMshDkwV+Xu_FjrKeg@mail.gmail.com/
> > [2]: https://lore.kernel.org/git/xmqqa68nlfiz.fsf@gitster.g/
>
> I think we are expecting a submission by Dscho to replace these two
> patches.
Oh? I thought Eric was on top of things much more than I am, I just tried
to provide clarity about the intentions behind the original wording.
Eric, please do feel free to Cc: me on any new iteration you want to send;
I won't be able to work on a patch to reword the `range-diff`
documentation.
Ciao,
Dscho
next prev parent reply other threads:[~2022-08-10 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 3:38 What's cooking in git.git (Aug 2022, #02; Fri, 5) Junio C Hamano
2022-08-07 3:02 ` Eric Sunshine
2022-08-08 13:46 ` Junio C Hamano
2022-08-10 9:26 ` Johannes Schindelin [this message]
2022-08-18 19:07 ` Eric Sunshine
2022-08-20 0:18 ` 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=o5340r34-027q-4ops-93o1-8368s4qropo5@tzk.qr \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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).