All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonin Godard <antonin.godard@bootlin.com>
To: "Kernel.org Tools" <tools@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Antonin Godard <antonin.godard@bootlin.com>
Subject: [PATCH b4 0/2] prep, diff: support overriding range-diff creation factor
Date: Tue, 04 Feb 2025 17:44:15 +0100	[thread overview]
Message-ID: <20250204-creation-factor-v1-0-9988d594a018@bootlin.com> (raw)

git range-diff allows to override the creation factor, which is
sometimes useful to adjust for seeing different diff outputs. This is
not possible with the current code, and is also not configurable from
git config.

Add an option to diff and prep to override the default creation factor
value.

I can update the doc in a v2 if needed.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
Antonin Godard (2):
      diff: add a creation factor argument
      prep: add creation-factor argument

 src/b4/command.py | 4 ++++
 src/b4/diff.py    | 7 ++++++-
 src/b4/ez.py      | 6 ++++--
 3 files changed, 14 insertions(+), 3 deletions(-)
---
base-commit: d23a9a2d5684369710bd2e416e41159193df3756
change-id: 20250127-creation-factor-ce8069a0bb3c

Best regards,
-- 
Antonin Godard <antonin.godard@bootlin.com>


             reply	other threads:[~2025-02-04 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 16:44 Antonin Godard [this message]
2025-02-04 16:44 ` [PATCH b4 1/2] diff: add a creation factor argument Antonin Godard
2025-02-04 16:44 ` [PATCH b4 2/2] prep: add creation-factor argument Antonin Godard
2025-02-06 18:09 ` [PATCH b4 0/2] prep, diff: support overriding range-diff creation factor Konstantin Ryabitsev
2025-02-07  7:58   ` 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=20250204-creation-factor-v1-0-9988d594a018@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.