From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Antonin Godard" <antonin.godard@bootlin.com>,
"Kernel.org Tools" <tools@kernel.org>
Cc: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH b4 v2 1/3] diff: add a creation factor argument
Date: Fri, 21 Feb 2025 09:25:01 +0100 [thread overview]
Message-ID: <D7XZAIZFFGAP.BGUHTUI8TMK7@bootlin.com> (raw)
In-Reply-To: <20250220-creation-factor-v2-1-7a0949a3a060@bootlin.com>
On Thu Feb 20, 2025 at 3:24 PM CET, Antonin Godard wrote:
> When using git range-diff it is possible to override the creation factor
> when git considers a large change a total rewrite (and so showing no
> diff at all), or a change so small it shouldn't be considered.
>
> This parameter is only possible to set from command-line, it has no
> global option associated to it within Git's config, so add a
> --creation-factor parameter to b4 to achieve the same behavior.
Gah, sorry, I forgot to update the commit titles/descriptions. I'll update that
in the next version.
Antonin
next prev parent reply other threads:[~2025-02-21 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 14:24 [PATCH b4 v2 0/3] prep, diff: support adding range-diff arguments Antonin Godard
2025-02-20 14:24 ` [PATCH b4 v2 1/3] diff: add a creation factor argument Antonin Godard
2025-02-21 8:25 ` Antonin Godard [this message]
2025-02-20 14:24 ` [PATCH b4 v2 2/3] prep: add creation-factor argument Antonin Godard
2025-02-20 14:24 ` [PATCH b4 v2 3/3] prep, diff: document the --range-diff-opts option Antonin Godard
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=D7XZAIZFFGAP.BGUHTUI8TMK7@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=konstantin@linuxfoundation.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tools@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.